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

Moving changes from dev to stage #17

Merged
merged 1 commit into from
Nov 15, 2024
Merged

Moving changes from dev to stage #17

merged 1 commit into from
Nov 15, 2024

Conversation

BryanFauble
Copy link
Contributor

Migrating up changes to stage api.

Testing:

  1. I ran the API tests against the dev environment. Once merged into stage I will do the same. Once that is completed I will ask IT to update DNS records for dev/stage to point to this deployment. Tom Yu will then run end-to-end tests through DCA.

…hematic branch (#16)

* Bumping resources closer to current deployment, point to latest rc schematic branch
@BryanFauble BryanFauble requested review from a team as code owners November 15, 2024 19:37
Copy link
Collaborator

@thomasyu888 thomasyu888 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥 LGTM!

@@ -18,20 +18,23 @@
"FQDN": "prod.schematic.io",
"CERTIFICATE_ARN": "arn:aws:acm:us-east-1:878654265857:certificate/d11fba3c-1957-48ba-9be0-8b1f460ee970",
"TAGS": {"CostCenter": "NO PROGRAM / 000000"},
"SCHEMATIC_CONTAINER_LOCATION": "ghcr.io/sage-bionetworks/schematic:v0.1.94-beta",
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will this deploy to prod on this pr or does it wokr like the previous repo, where pushing to prod branch triggers deploy to prod.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

where pushing to prod branch triggers deploy to prod.

That is correct. Only changes deployed to the "prod" branch will be deployed to prod. My thought behind having this configured like this is that ahead of time we could update these values. We can also limit the number of changes that might need to be separate in each long-lived branches to keep them all in sync. Meaning we can always move changes up from dev -> stage -> prod without much thought.

@BryanFauble BryanFauble merged commit ac1f4ca into stage Nov 15, 2024
9 checks passed
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