(EcsDeployAction): Optionally allow service_name
and cluster_name
as String
#32584
Labels
@aws-cdk/aws-ecr
Related to Amazon Elastic Container Registry
closing-soon
This issue will automatically close in 4 days unless further comments are made.
feature-request
A feature should be added or improved.
p2
response-requested
Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Describe the feature
Optionally allow
service_name
andcluster_name
asstr
type forEcsDeployAction
And change
service
(IBaseService
) to optionalUse Case
Creating an
ecs.FargateService
, which pulls an image from anecs.Repository
within the same Stack will fail, or hang (because there will not be an image in the new ECR)Example Stack:
EcsDeployAction
to ECS)The ECR Repository will create fine, but will be empty
The Fargate Service will launch fine (albeit failing to launch a container), and then the cdk/CloudFormation deploy hangs because the ECR is empty
The CodePipeline doesn't get created because the
EcsDeployAction
Depends on theIBaseService
type - even though it only needs the Service Name and Cluster Name, which can be provided as known Strings:https://github.com/aws/aws-cdk/blob/main/packages/aws-cdk-lib/aws-codepipeline-actions/lib/ecs/deploy-action.ts#L114-L115
Proposed Solution
Optionally allow:
https://docs.aws.amazon.com/cdk/api/v2/python/aws_cdk.aws_codepipeline_actions/EcsDeployAction.html
Other Information
No response
Acknowledgements
CDK version used
2
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: