GCP dev environment terraform configs #610
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ization for this example project. Doing so is outside scope and will easily take another 6 months to get quality terraform configs that set up an entire GCP organization
…initial network module
github-actions
bot
added
CI/CD
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Our initial IaC (re)setup and terraform configs. The PR adds a terraform directory for an example 'development' environment provisioning on Google Cloud (GCP).
no tests are added. Creating a CI workflow that checks fmt and terraform validation may prove difficult or impossible (further research needed) because the USEPA GitHub org does not allow using hashicorp resuable actions.
Issue ticket number and link
Checklist