Allow certs to be attached to specific processes. #1014
Merged
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.
Fixes #1013
With the addition of the
ports
key in the extended Procfile, it makes more sense to be able to attach a certificate to a process within the app, rather than the app itself. This is supported in the backend (CloudFormation scheduler), so this is just UI to expose it in the frontend.This will allow you to attach different certificates to different processes (only 1 cert per process is allowed, since that's the case with ELB/ALB).
This should be fully backwards compatible with older emp clients. If the
-p
flag isn't provided, it just defaults to attaching the cert to theweb
proc: