feat(ecs): add forceNewDeployment feature for ecs service #35726
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue # (if applicable)
Closes #27762
Reason for this change
Description of changes
This change introduces the forceNewDeployment feature for ECS services, which allows users to trigger a new deployment even when there are no service definition changes.
CFN public doc: https://docs.aws.amazon.com/AWSCloudFormation/latest/TemplateReference/aws-properties-ecs-service-forcenewdeployment.html
Describe any new or updated permissions being added
Description of how you validated changes
Note: I don't think we can add an integ-test for forceNewDeployment set to true as function generates a new nonce with each run which results in new CFN template.
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license