-
Notifications
You must be signed in to change notification settings - Fork 158
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: Environments #1095
Labels
Comments
I like it - how would that work with github deployments? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
One thing we're toying with internally is running multiple Empire instances that schedule jobs into the same cluster. We can use this to have a "production" environment, but also have a sub environment for "canary" deployments.
Having multiple Empire environments works well, however, there are a number of potential issues:
emp env
stays in sync.I think it would be interesting to think about what this could potentially look like if it was a first class feature inside Empire.
Currently, a "Release" within Empire basically represents a runnable package, including environment variables, for a service. It would be desirable to be able to take any release, and deploy it to an environment. Here's some psuedo UX for what this could look like:
In the above, the "canary" environment just means a separate private hosted zone (e.g.
.canary
instead of.empire
).The actual changes to support this within Empire internally wouldn't be very big, so it would just be mostly about UX.
I think there's also some questions around whether scaling configuration belongs in a release, since you may want to control that separately in different environments.
The text was updated successfully, but these errors were encountered: