-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
fix: reverse order of deployers during cleanup (#7284) (backport v1) #7927
fix: reverse order of deployers during cleanup (#7284) (backport v1) #7927
Conversation
a6f8c9e
to
3b14aa0
Compare
Codecov Report
@@ Coverage Diff @@
## v1 #7927 +/- ##
=====================================
Coverage ? 68.38%
=====================================
Files ? 563
Lines ? 26699
Branches ? 0
=====================================
Hits ? 18259
Misses ? 7173
Partials ? 1267 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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.
lgtm
3b14aa0
to
9bb5a0d
Compare
I moved the reversal function into it's own method and added tests. |
711190b
to
55795fa
Compare
I see, that I updated the wrong function in the rush of backporting it. Will fix this now. |
55795fa
to
382358c
Compare
.tool-versions is used by asdf (package manager) to set the go version for this repository
382358c
to
3602642
Compare
Fixes: #7284
Related: Relevant tracking issues, for context
Merge before/after: Dependent or prerequisite PRs
Description
Add a new deployer slice during cleanup function of the DeployerMux which is reversed in it's order. This change should be covered by the existing unittests since no new function was added.
This is a backport for v1.
User facing changes (remove if N/A)
Before:
Modules are undeployed in the same order as they are deployed. Visible in the console as
After:
Modules are undeployed in reverse order.