The AWS pass-development account is being used to test deployments of the PASS infrastructure stack. Now that the underlying layers are stabilizing, it is becoming a useable target Environment option for application testing in https://github.com/jhu-library-devops/JHU-PASS-Deployment.
Why?
Beyond the testing of IAC, the environment could also be used as a testing/unstable alternative to Staging.
How?
In terms of what specifically would need to be added, I've noted there is
A workflow file per environment, which pass off to modular deploytoAWSworkflows and python scripts.
The environment defined at the GitHub project level with secrets from the aws account.
Acceptance Criteria
A deployment action should be successful with artifact payloads in the proper destinations; since the TF code is still in development it may be too soon to expect a fully-functional application to result from it.
What?
The AWS pass-development account is being used to test deployments of the PASS infrastructure stack. Now that the underlying layers are stabilizing, it is becoming a useable target Environment option for application testing in https://github.com/jhu-library-devops/JHU-PASS-Deployment.
Why?
Beyond the testing of IAC, the environment could also be used as a testing/unstable alternative to Staging.
How?
In terms of what specifically would need to be added, I've noted there is
A workflow file per environment, which pass off to modular deploytoAWSworkflows and python scripts.
The environment defined at the GitHub project level with secrets from the aws account.
Acceptance Criteria
A deployment action should be successful with artifact payloads in the proper destinations; since the TF code is still in development it may be too soon to expect a fully-functional application to result from it.
Related Issues