-
Notifications
You must be signed in to change notification settings - Fork 210
Support ecs quicksync force new deployment config #6336
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
Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com>
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #6336 +/- ##
==========================================
- Coverage 28.83% 28.81% -0.02%
==========================================
Files 560 560
Lines 59922 59937 +15
==========================================
- Hits 17277 17271 -6
- Misses 41324 41345 +21
Partials 1321 1321
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
t-kikuc
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.
LGTM, let's try
pkg/app/piped/executor/ecs/deploy.go
Outdated
| forceNewDeployment := e.appCfg.QuickSync.ForceNewDeployment | ||
|
|
||
| // Store force new deployment flag to metadata store. | ||
| e.Input.MetadataStore.Shared().Put(ctx, "force-new-deployment", strconv.FormatBool(forceNewDeployment)) |
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.
nit: use a const for the key
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.
Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com>
This reverts commit cac601e.
This reverts commit cac601e. Signed-off-by: khanhtc1202 <khanhtc1202@gmail.com>
What this PR does:
Add ECS QuickSync forceNewDeployment config. The configuration would be like:
Why we need it:
It requires forcing a new deployment when updating the ECS service configuration from LaunchType to Capacity provider strategy. So, my plan is to support switching from launch type to capacity provider strategy on existing service by enabling force new deployment on the updated service in case of ECS quick sync deployment triggered.
Error message
Which issue(s) this PR fixes:
Follow PR #6331
Does this PR introduce a user-facing change?: