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

Merge to Main - Production deployment #557

Merged
merged 5 commits into from
May 3, 2021
Merged

Merge to Main - Production deployment #557

merged 5 commits into from
May 3, 2021

Conversation

afred
Copy link
Contributor

@afred afred commented May 3, 2021

First attempt at a continuous deployment merge since:

  1. introducing the main branch (which will replace master after this works)
  2. fixing the Travis config for using AWS CodeDeploy to trigger deployments after successful builds.

afred and others added 5 commits April 22, 2021 21:31
* Changes branch condition to match 'develop' for deployment to Demo stack.
* Adds deploy config to deploy to Prod stack when branch is 'main'.
The problem was that the script trying to fetch deployment info was using AWS credentials
for the user who has permissions on S3, but not CodeDeploy.

This uses a different set of credentials which it expects to be correctly set in the
environment. If the expected env vars are empty, the error message will say say.
When on an Asset page, add .xml to the GUID and get the PBCore XML back.
@foglabs foglabs merged commit 48c4b38 into main May 3, 2021
orangewolf pushed a commit to notch8/ams that referenced this pull request Aug 30, 2022
Merge to Main - Production deployment
orangewolf pushed a commit to notch8/ams that referenced this pull request Aug 30, 2022
Merge to Main - Production deployment
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.

2 participants