-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implementation of WFJT limit & SCM_branch prompting #4369
Implementation of WFJT limit & SCM_branch prompting #4369
Conversation
recheck |
f2aa581
to
f112cf3
Compare
7bd8784
to
e51c410
Compare
63b098d
to
adb736e
Compare
This implementation is still a half-way move toward making WFJTs full "config" objects. Basically, we have the opportunity to remove some of the really back hacks that had to be implemented for sliced jobs. See: awx/awx/main/models/workflow.py Lines 232 to 240 in 76a1099
I'm resisting doing a much broader refactor to get rid of this. Ideally this would use |
adb736e
to
d8f26ec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great - I did find one scenario that's not covered in the UI currently. If you create a workflow and prompt for limit on launch (make sure this is the only promptable thing on the workflow) and launch that workflow, the prompt modal isn't shown and the job is simply launched. In order to fix this I think we need to change https://github.com/ansible/awx/blob/devel/awx/ui/client/lib/models/WorkflowJobTemplate.js#L57 to
return (
launchData.can_start_without_user_input &&
!launchData.ask_inventory_on_launch &&
!launchData.ask_variables_on_launch &&
!launchData.survey_enabled &&
!launchData.ask_scm_branch_on_launch &&
!launchData.ask_limit_on_launch &&
launchData.variables_needed_to_start.length === 0
);
Note the addition of !launchData.ask_limit_on_launch &&
to that conditional. Otherwise I think this is looking good. I tested out the workflow node scenarios and ran into #4293 but that should be addressed by #4525
d8f26ec
to
d98808f
Compare
Thanks, good catch! I was easily able to replicate this situation manually and confirmed that the latest commit fixes it. While doing this, I noticed another odd thing - I couldn't set it to prompt for limit while creating the WFJT. That turned out to be because it was missing in yet another place. Also confirmed fixed in last commit. |
Build succeeded.
|
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking really solid. Pinging @squidboylan on a final call for this on QE side, looks good from UI end.
e3b6f67
to
6913b6d
Compare
Build succeeded.
|
6913b6d
to
70fc1b6
Compare
Build succeeded.
|
70fc1b6
to
9f5b7c2
Compare
Build failed.
|
recheck |
Build succeeded.
|
add feature to UI and awxkit restructure some details of create_unified_job for workflows to allow use of char_prompts hidden field avoid conflict with sliced jobs in char_prompts copy logic update developer docs update migration reference bump migration
bump migration bump migration again
9f5b7c2
to
e3c1189
Compare
Build succeeded.
|
Build succeeded (gate pipeline).
|
SUMMARY
Connect #1731
Does not yet do #1845
There will also be a need to apply this to #282
I believe that 282 will be in scope near-term, but 1845 will not.
ISSUE TYPE
COMPONENT NAME
AWX VERSION
ADDITIONAL INFORMATION
Heads up to @jbradberry, this is about as simple as this material is going to get, and that's not very simple. This does the abuse of Django character fields to make them nullable, and tries to make it so that
scm_revision
will follow suit in a relatively consistent pattern.