Skip to content
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

Merged
merged 5 commits into from
Nov 27, 2018

Conversation

griggheo
Copy link
Contributor

@griggheo griggheo commented Nov 13, 2018

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.

@griggheo griggheo requested a review from aldeed November 13, 2018 22:06
propel-feat.yaml Outdated
port_mappings:
- container_port: 8082
host_port: 8082
image: sportsdirect/nginx
Copy link
Contributor

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?

Copy link
Contributor Author

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.

@aldeed
Copy link
Contributor

aldeed commented Nov 15, 2018

Seems OK as far as I can tell. Just one question, and I'm rerunning app tests that failed. Probably just a random failure.

@spencern
Copy link
Contributor

Failed with

Waiting for CF stack "staging-service-reaction-core" to be updated
CreateRelease: DeployReleaseForService: Error waiting for CF stack "staging-service-reaction-core" to be updated: ResourceNotReady: failed waiting for successful resource state

during deploy to ecs release branch

@griggheo
Copy link
Contributor Author

Yup looking at it. Looks like AWS user permissions.

@griggheo
Copy link
Contributor Author

I fixed the IAM permissions for the user running propel from CircleCI and the deployment worked.

@spencern spencern merged commit 2d614b9 into release-2.0.0-rc.7 Nov 27, 2018
@spencern spencern deleted the release-2.0.0-rc.7-gg-propel-changes branch November 27, 2018 17:57
@spencern spencern mentioned this pull request Jan 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants