Add Tier 3 Workload Templates and Stand Alone Script. #220
Conversation
| terraform { | ||
| required_providers { | ||
| azurerm = { | ||
| source = "hashicorp/azurerm" | ||
| version = "= 2.55.0" | ||
| } | ||
| } | ||
| } | ||
|
|
There was a problem hiding this comment.
Any reason to explicitly indicate the provider here? I think the pattern we've been following is to set this at the root module and have the configurations from /modules/* inherit from their caller.
There was a problem hiding this comment.
Without it I'm currently getting this warning:
╷
│ Warning: Provider azurerm is undefined
│
│ on main.tf line 136, in module "t3-inbound-peering":
│ 136: azurerm = azurerm.hub
│
│ Module module.t3-inbound-peering does not declare a provider named azurerm.
│ If you wish to specify a provider configuration for the module, add an entry for azurerm in the required_providers
│ block within the module.
╵
If you know some other secret to suppressing it, I can do that instead. But it appears anytime we're going to pass in more than one configured provider we might need to define this block.
There was a problem hiding this comment.
Huh, odd. Some things I instantly start to consider: Do we get that warning when sourcing the hub provider for the resource group and virtual network in the root tier-3 module? Do we get that warning when deploying the virtual-network-peering with the hub provider in tier-0 through tier-2?
There was a problem hiding this comment.
The error appears on every deployment that uses network-peering, specifically anything where we peer the SACA hub to the current tier. This will be a non-issue relatively soon.. but the way we had it before the network resource needed to have the SACA hub provider so it could create the network resource.
|
be sure to update the PR title to something descriptive, this is what makes it into the git log 👍 |
Wait, it's already there. I missed it the first time. Sorry. 😄 |
Co-authored-by: Glenn Musa <[email protected]>
Breanna-Stryker
changed the title
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Glenn Musa <[email protected]>
Co-authored-by: Brooke Hamilton <[email protected]>
Co-authored-by: Brooke Hamilton <[email protected]>
Co-authored-by: Brooke Hamilton <[email protected]>
* Copy tier template for 3 * Bare minimum setup for deploying a tier 3 * Docs. * Update src/scripts/config/generate_config_file.sh Co-authored-by: Glenn Musa <[email protected]> * Update src/scripts/terraform/create_globals_from_config.sh Co-authored-by: Glenn Musa <[email protected]> * Update src/scripts/config/generate_config_file.sh Co-authored-by: Glenn Musa <[email protected]> * Link to workload doc from the getting started doc * fix tier3 var usage * Update src/docs/workload-deployment.md Co-authored-by: Brooke Hamilton <[email protected]> * Update src/docs/workload-deployment.md Co-authored-by: Brooke Hamilton <[email protected]> * Update src/docs/workload-deployment.md Co-authored-by: Brooke Hamilton <[email protected]> * Fixed links * Fixed link Co-authored-by: Bree Stryker <[email protected]> Co-authored-by: Glenn Musa <[email protected]> Co-authored-by: Brooke Hamilton <[email protected]> Co-authored-by: Brooke Hamilton <[email protected]>
Description
This is a quick implementation of adding a tier 3. Things like automatically performing additive deployments aren't available yet and will need to be considered when re-architecting the system.
Changes include adding tier3 variables where possible to be used for a quick deployment, as well as a template set, and a script for deploying a tier 3. deploy_t3.sh scrapes together various sections of other scripts to automate the deployment and application of the tier.
Issue reference
The issue this PR will close: #10
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list:
shellcheck.vscode/extensions.json.)