You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the containerName uses the options.service string, which is configured by the watchbot client. Since the string is not created using CloudFormation helper functions, the containerName cannot be customised based on the stack name. This means that if multiple stacks are running on the same service, the containerName reflects the service name and not the stack name and this can be confusing if you're parsing Cloudtrail logs and looking for containers of a specific stack.
Currently, the
containerName
uses theoptions.service
string, which is configured by the watchbot client. Since the string is not created using CloudFormation helper functions, thecontainerName
cannot be customised based on the stack name. This means that if multiple stacks are running on the same service, the containerName reflects the service name and not the stack name and this can be confusing if you're parsingCloudtrail
logs and looking for containers of a specific stack.To fix, we can change
ecs-watchbot/lib/template.js
Line 667 in c950b97
Fn::Join
cc/ @mapbox/platform-engine-room
The text was updated successfully, but these errors were encountered: