[WORKFLOWS-85] Prototype Tower project in separate account #84
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.
While I'm waiting for the STRIDES AMP-AD account to be created, I wanted to prototype the deployment of a Tower project to a separate account. In this PR, I'm using sandbox, but the intent is to switch to the new AMP-AD account once it's available. The benefit is that all compute and storage costs would get charged to NIH directly.
Note that most of the "file changes" are files being renamed because I streamlined the GitHub Actions workflow. I've adopted what @tthyer did for BridgeDownstream, and to make it extra streamlined, I'm using prefixes and suffixes for the Sceptre stack groups.
Depends on Sage-Bionetworks-IT/organizations-infra#339