-
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
Add UI support for management jobs in workflows #10572
Conversation
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.
Some things I found:
-
if you type/edit the days field it then shows up as a string in the variable details view after clicking on the
i
icon when hovering a node. However, when you edit that same node, but don't edit the days field the number appears as an integer in the variables detail after clicking on thei
icon. There doesn't seem to be any negative impact on functionality, just some ux inconsistency. -
We don't seem to show the convergence data in the detail modal. Should we?
-
Create a
Clean up job details
node and connect it to aCleanup expired sessions
node. Then click on theCleanup expired sessions
nodei
icon. Page crashes.
02d79a4
to
aba0340
Compare
Build succeeded.
|
Will include a fix for this
Was probably just missed when we did the initial work. Let's file an issue for this.
The api expects the key to be I'd propose changing the string to something like: so that it more closely matches the other interface.
I'll look at this |
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.
This looks good to me. The unit tests pass, and the issues described earlier are resolved. I'm triggering e2e tests now.
@mabashian could you rebase this one? |
8baf4cf
to
6935b0e
Compare
6935b0e
to
5f7db08
Compare
return t`This field must be a number and have a value less than ${max}`; | ||
} | ||
if (!Number.isFinite(max) && value < min) { | ||
return t`This field must be a number and have a value greater than ${min}`; |
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.
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
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.
Verified that mgmt jobs can be added as nodes to a workflows and run it, also tested the scheduled workflow with mgmt jobs.
Hide management job for non system admin as node type choice. Also, fix related uni-tests related to this change. See: ansible#12334 Also: ansible#10572
Hide management job for non system admin as node type choice. Also, fix related uni-tests related to this change. See: ansible#12334 Also: ansible#10572
SUMMARY
link #790
This has been supported via the API for a long time. The tricky part was handling the
days
(days to keep) for some of the management jobs. That value needs to flow in/out of extra_data so it's a bit different from other workflow node fields.Here it is in action:
I elected to just show the variables in the details view for simplicity. If it's important we could pull
days
out of the object but more code brings added risk of bugs 🤷 .@wenottingham if you're not really into this as a feature that's fine - we can close this and reference it later.
ISSUE TYPE
COMPONENT NAME