-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ecs: ContainerDefinition.addEnvironment #2559
Comments
+1 |
I was able to hack around this like so, but your mileage may vary: (service.taskDefinition.defaultContainer as any).props.environment["ENV_VAR_FOO"] = "bar"; |
Somewhere between CDK v1.122.0 and v1.144.0 my workaround above stopped working. This is what I now have to use instead: (service.taskDefinition.defaultContainer as any).node.host.environment["ENV_VAR_FOO"] = "bar"; |
This was in fact resolved via #17889 |
|
It's very useful to be able to mutate the environment configuration of the container definition, similar to Lambda.
The text was updated successfully, but these errors were encountered: