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

Feature request: cluster-wide ENV definitions #347

Open
kylev opened this Issue Mar 17, 2016 · 6 comments

Comments

Projects
None yet
8 participants
@kylev

kylev commented Mar 17, 2016

Use case: I'm running a mix of ECS, EC2, and AWS resources like RDS and ElastiCache. I have separate staging and production environments on different VPCs. Right now, to convey the connection URL for my ElastiCache redis instance, I have to set an environment variable REDIS_HOST on every single task definition that I create. It's different for staging vs. production, so this means I have to create different tasks for every container in every environment. This is manageable with automation, but also a bit overly complex.

Another use case would be setting RUBY_ENV or RAILS_ENV for every task.

Proposed solution: Add the ability to define env variables per ECS cluster, and have them applied to all containers run within that cluster.

@bobziuchkovski

This comment has been minimized.

Show comment
Hide comment
@bobziuchkovski

bobziuchkovski May 19, 2016

Yes, I would absolutely love to see this as well. I'm in a similar situation using CloudFormation input params and wiring those to ENV vars passed to ECS task definitions. Right now that means 60 env vars duplicated in the CloudFormation template for every task definition. I'm currently trying to think through possible workarounds, but supporting this out of the box would make life much, much simpler.

bobziuchkovski commented May 19, 2016

Yes, I would absolutely love to see this as well. I'm in a similar situation using CloudFormation input params and wiring those to ENV vars passed to ECS task definitions. Right now that means 60 env vars duplicated in the CloudFormation template for every task definition. I'm currently trying to think through possible workarounds, but supporting this out of the box would make life much, much simpler.

@JustinAiken

This comment has been minimized.

Show comment
Hide comment
@JustinAiken

JustinAiken commented May 19, 2016

👍

@voxxit

This comment has been minimized.

Show comment
Hide comment
@voxxit

voxxit commented May 19, 2016

👍

@hwrdprkns

This comment has been minimized.

Show comment
Hide comment
@hwrdprkns

hwrdprkns commented May 20, 2016

👍

@breath103

This comment has been minimized.

Show comment
Hide comment
@breath103

breath103 Jun 13, 2016

👍
we're running sidekiq on ECS and this is almost insane thing to update env for every each services, update service version, kill existing task.
especially if you have like 6 services.

breath103 commented Jun 13, 2016

👍
we're running sidekiq on ECS and this is almost insane thing to update env for every each services, update service version, kill existing task.
especially if you have like 6 services.

@panga

This comment has been minimized.

Show comment
Hide comment
@panga

panga commented Sep 27, 2016

+1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment