Deploy develop branch to staging environment in ECS #355
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
|
I'm not sure if this comment is the right place to put it but it's related to our staging url Currently, the app shows that we are using
Can we get a Segment test key and include it in the staging URL? It will help the team test internally, and also make it easier to demo Segment integration. |
…tarterkit into circleci-propel-ecs
…tarterkit into circleci-propel-ecs
Merged
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.
Impact: major
Type: feature
Issue
The CircleCI pipeline has been modified to use the latest version of the propel CLI in order to push the develop branch to the staging environment.
Breaking changes
Testing