feat(ecs): add codepipeline deploy-action to ecs cluster #2049
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.
This will implement #1386
No Unit-Test, one Integration Test ist present. The similar compontent
s3 deploy-action
has no unit-test (didnt found it), so I oriented there. Please give me feedback when required.I have tested the integration test in my private AWS Account, and it worked.
Notes:
toCodePipelineInvokeAction
(on service?) asservice
andrepository
is required, as I didnt figured out an easy api for this. Need feedback if this is required.ecs:*
for*
), I oriented on the default AWS CodePipeline Role: https://docs.aws.amazon.com/codepipeline/latest/userguide/how-to-custom-role.htmlsts:AssumeRole
andiam:PassRole
for*
- same reason as point before. The following would be ideal, but I didnt figured out how to construct this with cdk:Pull Request Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.