-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Factorize some identical playbooks steps into their own sub-playbooks #10633
Factorize some identical playbooks steps into their own sub-playbooks #10633
Conversation
Hi @VannTen. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
9176154
to
069f4e1
Compare
069f4e1
to
0e3a07d
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.
@VannTen Thank you, lgtm 👍
/uncc @jayonlau @oomichi If you have some bandwith for a rewiew 🙏 |
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!
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: floryut, MrFreezeex, VannTen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…kubernetes-sigs#10633) * Factorize identical playboooks steps in sub-playbooks * Copy legacy_groups.yml into its sole user
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Move around some plays in
playbooks/
into their own sub-playbooks so we havean easier time making more involved refactoring later on (like: converting to
dynamic includes to avoid so many skipped tasks).
Which issue(s) this PR fixes:
N/A
Special notes for your reviewer:
Does this PR introduce a user-facing change?: