-
Notifications
You must be signed in to change notification settings - Fork 0
Implement disabled reason for flow #782
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
base: main
Are you sure you want to change the base?
Conversation
GitLab Pipeline ActionGeneral informationLink to pipeline: https://gitlab.com/code0-tech/development/sagittarius/-/pipelines/2220856753 Status: Passed Job summariesrspec: [ee]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/12476009009/artifacts/tmp/coverage/index.html rspec: [ce]Coverage report available at https://code0-tech.gitlab.io/-/development/sagittarius/-/jobs/12476009007/artifacts/tmp/coverage/index.html rubocop724 files inspected, no offenses detected |
bcd4797 to
2524e50
Compare
2524e50 to
bead536
Compare
| argument :type, Types::GlobalIdType[::FlowType], required: true, | ||
| description: 'The identifier of the flow type' | ||
|
|
||
| argument :disabled_reason, String, |
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.
I wouldn't have exposed this to the user because the reason would for example be used when a flow gets disabled because the namespace reached its execution quota and we don't want the user to re-enable the flow themself by just removing the disabled_reason.
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.
I thought thats a user string to disable the flow, maybe we should add translations there for different messages, like quota and other stuff
close #781