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

Apocalyptic testing framework #953

Merged
merged 2 commits into from
Nov 13, 2024
Merged

Conversation

shawncrawley
Copy link
Collaborator

@shawncrawley shawncrawley commented Nov 12, 2024

Refs #938
Takes an initial stab at the apocalyptic testing framework. This scatters a bunch of count = var.environment == "ti" ? X : Y logic throughout the main.tf scripts. This shuts off all live workflow feeds and also includes a new Testing module when deploying to "ti". The testing module sets up an Event Bridge trigger that detects new files showing up at s3://hydrovis-ti-deployment-us-east-1/common/data/model/com/nwm/prod/nwm.YYYYMMDD/ and then triggers the viz_initialize_pipeline Lambda function. Terraform is also used to make a copy of all the apocalyptic test datasets that are statically in place at s3://hydrovis-ti-deployment-us-east-1/test_nwm_outputs/ and move them into the trigger location. Thus, the terraform code should both deploy all resources and then kick off the tests.

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