Hardcoding the Azure location #125
christophetd
announced in
Decision logs
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Context
As part of adding support for Azure (thanks to @rcobb-scwx), we identified that the Azure Terraform provider behaves differently than the AWS one.
More precisely:
When using Azure, the typical use-case is to create a resource group (in a specific location), and then provision resources in this resource group:
In particular, the
location
argument is mandatory and cannot be sourced from environment.Problem
The current behavior for AWS is to not handle any region in the Stratus Red Team code, and instead let the user configure his environment or AWS configuration file as they prefer:
For Azure, we can't follow this model.
Options
Option 1: Hardcode the Azure location name
Pros: Simple
Cons: Magic values, not configurable, would be challenging to change.
Option 2: Allow the user to specify an Azure location through an environment variable
Pros: Configurable (potentially with a default)
Cons: Requires adding functionality to the core to start passing Terraform input variables to the Terraform code of individual attack techniques.
Decision
Hardcode the Azure location name. Supporting factors:
Beta Was this translation helpful? Give feedback.
All reactions