-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
ECS deployment: move TLS certificate ARN from propel.yaml to ENV vars #4802
ECS deployment: move TLS certificate ARN from propel.yaml to ENV vars #4802
Conversation
propel-feat.yaml
Outdated
port_mappings: | ||
- container_port: 8082 | ||
host_port: 8082 | ||
image: sportsdirect/nginx |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is sportsdirect/nginx
correct for this repo?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I fixed it.
Seems OK as far as I can tell. Just one question, and I'm rerunning app tests that failed. Probably just a random failure. |
Failed with
during deploy to ecs release branch |
Yup looking at it. Looks like AWS user permissions. |
I fixed the IAM permissions for the user running propel from CircleCI and the deployment worked. |
Resolves #issueNumber
Impact: breaking
Type: refactor
Issue
The syntax for the configuration file for the CLI tool propel has been changed so that the TLS Certificate ARN can be specified via an ENV variables and not hardcoded in the configuration file.
Solution
One-line change to the propel.yaml file.
Breaking changes
This is a breaking change in that old propel configuration files will break the deployment process.
Testing
Make sure staging is accessible after a deployment.