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

Issues for 1.0 #89

Open
5 tasks
pbashyal-nmdp opened this issue Aug 14, 2023 · 2 comments · Fixed by #90
Open
5 tasks

Issues for 1.0 #89

pbashyal-nmdp opened this issue Aug 14, 2023 · 2 comments · Fixed by #90

Comments

@pbashyal-nmdp
Copy link
Contributor

pbashyal-nmdp commented Aug 14, 2023

Issues for 1.0

@chrisammon3000
Copy link
Contributor

chrisammon3000 commented Aug 15, 2023

Some considerations for task # 2 (New Makefile target make vpc that builds the network (optional)):

If multiple gfe-db environments are be created in the same account, some environment variables will need to be different to avoid conflicts, so 1) there should be a way to manage this locally 2) we will want safeguards in place to prevent deploying using the wrong environment variables 3) Resource name conflicts will have to be addressed

  1. Managing environments locally
    One solution I would offer is to use multiple .env:
.env.dev
.env.qa
.env.prod

Where we append the $STAGE variable to .env.env.${STAGE} in the Makefile so it only includes those variables.

  1. Safeguards against deploying to the wrong environment
  • Print the environment to the console and ask user to confirm before deploying or updating, the user should confirm that they are deploying with the correct $STAGE value
  • Create a change set and ask user for confirmation before updating
  • CloudFormation stacks are now tagged with the git branch, so we can detect if a deployment update is being made from a different branch than what the tag is and ask for user confirmation before continuing. (Deploying the wrong branch to the wrong environment will cause problems)
  1. Avoiding resource name conflicts
    Shouldn't be an issue as long as every named resource has the $STAGE variable in it's name.

@chrisammon3000
Copy link
Contributor

chrisammon3000 commented Aug 22, 2023

Tasks 1 & 2 are ready for review:

The points I mentioned above for managing environments locally, safeguard against deploying to the wrong environment, and avoiding resource name conflicts are implemented.

Task 3 (Keep track of IMGT commits to GFE DB) just needs to be merged with the most recent PRs first. It includes validation (task # 4) of build outputs and load results but does not include testing yet.

@chrisammon3000 chrisammon3000 linked a pull request Sep 4, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants