-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
KS-205: add workflow name to spec #13265
Conversation
1a4faab
to
fef2c56
Compare
fef2c56
to
23670e3
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.
Do you want to clean up commented out code?
Also several tests are failing.
5b8e953
to
3e8e399
Compare
a7c4a45
to
c33f8ca
Compare
@@ -78,6 +78,8 @@ type ORM interface { | |||
|
|||
DataSource() sqlutil.DataSource | |||
WithDataSource(source sqlutil.DataSource) ORM | |||
|
|||
FindJobIDByWorkflow(ctx context.Context, spec WorkflowSpec) (int32, error) |
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.
nit: a fully-descriptive name would be FindJobByWorkflowNameAndOwner but it's annoyingly long.
Quality Gate passedIssues Measures |
* KS-205: add workflow name to spec * fix test * fix sql and test * fix tests * remove empty wf owner,name check * fix bad merge of main * rename migration --------- Co-authored-by: Bolek <[email protected]>
Adds WorkflowName to the spec
This in turn is used on the node to ensure that (owner, name) are unique, which is important for job management.