-
Notifications
You must be signed in to change notification settings - Fork 4
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
[CZID-8390] Add sqs step notifications #116
Conversation
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 like the plugin overall. My high level ask is a change to an SNS based approach that should actually be pretty similar to what you have and very slightly simpler. See my review comment.
"TaskName": {"DataType": "String", "StringValue": run_id[-1]}, | ||
"ExecutionId": { | ||
"DataType": "String", | ||
"StringValue": "execution_id_to_be_passed_in", |
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.
How does this get populated? You should be able to pass this as an env variable in the step function definition.
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 was thinking we could also make this a WDL input & set it when the workflow starts. Either one is fine with me. We also want to use the Run Id here instead of the Execution Id
black
on the test/test_wdl.py file