Create ALIAS records for each exposed process #1005
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
phobologic
approved these changes
Oct 7, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also closes #796
For every process that is exposed, an ALIAS record will be created as
<process>.<app>.<zone>that points to the load balancer.For backwards compatibility, I'm keeping the special case CNAME that is created for
<app>.<zone>for "web" procs, but I think moving forward, the more specific<process>.<app>.<zone>record should be used. If a less specific<app>.<zone>is desired, it can be created outside of Empire to point to<process>.<app>.<zone>, which can make transitioning between different processes (without downtime) very easy (e.g. if you want to switch to an ALB, you can create a newweb2process that uses an ALB, then update<app>.<zone>to point toweb2.<app>.<zone>)