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
{{ message }}
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.
I'm switching my application's deployment to CodePipeline and the ECS. Is there a way using this API to update the container's environment variables? Previously I was using the CLI to register the task definition as follows:
And whatever variables were set in environment.json would be loaded into the container. I can't find any documentation describing how to set this using CloudFormation. Any ideas?
The text was updated successfully, but these errors were encountered:
Hi! The native CodePipeline -> ECS integration will only update the container definitions' image attribute so you cannot use it to manage environment variables. Luckily, you have a couple of other options:
You can use a Lambda function instead to drive your deployment and do something similar to the above to edit both the image and environment attributes.
If you're using CloudFormation to manage your task definition and service, you can use these templates to manage those fields instead of the native integration. See the documentation for more details and a previous iteration of this refarch for an example.
I'm switching my application's deployment to CodePipeline and the ECS. Is there a way using this API to update the container's environment variables? Previously I was using the CLI to register the task definition as follows:
And whatever variables were set in
environment.json
would be loaded into the container. I can't find any documentation describing how to set this using CloudFormation. Any ideas?The text was updated successfully, but these errors were encountered: