-
Notifications
You must be signed in to change notification settings - Fork 26
Split actions into reusable steps (fixes #213, fixes #77, embeds #233, #236, #253) #232
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
Conversation
f2dcb06 to
5fb2110
Compare
bsieber-mozilla
left a comment
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.
Thanks for the efforts in this PR and #233.
I think we can land this and iterate on this "pipeline" approach we discussed in the meeting today.
grahamalama
left a comment
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.
Looks good! I'm approving this knowing that #233 is a fast follow and we'll be quickly iterating on this design, but these were just things I wanted to comment on for posterity if for nothing else.
That's a good idea! |
…ors) (#236) * Rename ActionLogContext to ActionContext * Rename log_context to context * Remove := operator and chain operations * Remove the maybe_ from services.jira * Align signatures of action functions * Do not duplicate parameters between init and call * Runner now instantiates context * Pass actions contexts to action tests * Update actions docs * Remove redundant parameters * Adjust parameters between default.py and jira.py * Inherit JiraContext from Context * Remove useless and confusing condition * Replace repetitive calls with list of steps * Let the runner set the ActionContext operation * Reintroduce maybe_ for optional steps * Load default action steps from configuration (#253) * Move steps to jbi.actions.steps * Rename test_default to test_steps * Move test_default_with_assignee_and_status into test_steps * Load default action steps from configuration * Add tests for the default action behaviour * Rename groups of steps. create -> new, update -> existing * Remove default value config/config.prod.yaml Co-authored-by: bsieber-mozilla <[email protected]> * Move remapping of steps into helper * Remove useless pylint annotation * Adjust docstrings * Merge unspecified groups with default ones * Update secrets baseline Co-authored-by: bsieber-mozilla <[email protected]> Co-authored-by: bsieber-mozilla <[email protected]>
…ion-into-functions
fixes #213
I removed some of the class-based stuff, but not everything, we should agree on a design for #77 before we can go further IMO