search

eddmann / serverless-fargate

Maintain long-running Fargate ECS tasks within your Serverless project
51 stars 21 forks source link

Other resources depending on these services #55

Open Avadakedvr opened 3 months ago

Avadakedvr commented 3 months ago

While there is a dependsOn property to ensure certain resources are created before anything serverless-fargate creates, what about resources that must be created after anything serverless-fargate creates such as autoscaling policies? This is especially tricky because the logical IDs are generated via a manipulated string that includes the task name - hard to predict/use especially for feature branches - i.e. if the feature branch name is part of the task name!

You should create an option to allow the user to specify the logical ID of the AWS::ECS::Service resource and all other resources created by this plugin i.e. instead of manipulated task.name + "Service" here!

eddmann commented 1 month ago

Thanks for the raising this as an issue, just wondering have you put any thought into how you think the possible configuration could look?