-
Notifications
You must be signed in to change notification settings - Fork 789
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 ability to terminate execution of a step-fn state machine #1695
Conversation
Looking at test failures... |
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.
had a quick look so far, a few comments but overall looking good. I'll take this for a spin tomorrow when I have more time.
@saikonen can you confirm if you don't need the |
tested this and the token authorization and user/owner checks are working correctly. The issue with testing this is that the production token is cached locally, so in order to test a case where both user and token do not match, you need to invalidate the locally cached token |
Testing[619] @ d7400b1 |
@@ -614,6 +618,83 @@ def _token_instructions(flow_name, prev_user): | |||
) | |||
|
|||
|
|||
@step_functions.command(help="Terminate flow execution on Step Functions.") |
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.
minor nit - but for consistency AWS Step Functions
. not blocking for merging this PR in, but would be good if you can sweep this and various CLIs to polish up the help strings and make them consistent.
This PR should over-ride #1596
Usage:
python flow.py step-functions terminate sfn-d41004cd-1bbf-4c25-b284-94bfc921d78b