-
Notifications
You must be signed in to change notification settings - Fork 12
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Environment
- AAP Version: 2.4 (Issue also observed in 2.5 with aap_configuration )
- Ansible Collection:
infra.controller_configuration
v2.11.0 (latest)
Issue Summary
When using filetree_create
to export Workflow Job Templates (WJTs) and then using dispatch
to recreate them, the process works as expected. However, attempting to delete the WJTs using dispatch
fails, leaving behind an empty, non-functional Workflow still present in the AAP Controller.
Steps to Reproduce
- Export configuration using
filetree_create
withflatten_output: true
:ansible-playbook filetree_create.yml -e '{output_path:/path/to/output, flatten_output:true}'
- Manually delete the workflow in the UI (this step is facultative)
- Use
dispatch
to recreate WJTs from the generatedworkflow_job_templates.yaml
→ Works as expected. - Attempt to delete WJTs using
dispatch
→ Workflow itself remains, though JTs are removed.
Root Cause Analysis
- The exported
workflow_job_templates.yaml
setsstate: "present"
for all WJTs. dispatch
does not remove WJTs unless theirstate
is explicitly set to"absent"
.- The documentation states that
controller_state
determines whether objects are created or deleted but does not mention thatstate
must be manually modified for deletion. - Removing
state
fromworkflow_job_templates.yaml
causes a playbook error.
Proposed Fix
filetree_create
should either:- Omit the
state
field for WJTs (aligning with how JTs are handled). <- Preferred method - Document that
state
must be manually changed to"absent"
for deletion.
- Omit the
Thank you!
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working