You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are variables that exist in the settings module that are not available as variables in the TFE modules (Azure, AWS, GCP). One example is force_tls. Please audit the TFE modules' root variables.tf and main.tf to ensure that every variable that is available in the settings module of this repository is available to configure in each of the TFE modules.
Who is the audience for this request?
Everyone because everyone who uses the golden-path modules is affected by this.
What would the ideal solution look like?
Every variable in this settings module is available for configuration in the three TFE golden path modules.
What alternatives have you considered?
n/a
How does this impact you?
As a TFE engineer, I am not able to change certain settings for test/dev environments without branching off of the TFE modules' default branch. This also means, however, that tests are not able to configure these settings.
Are there any deadlines?
no
Is there any additional context?
n/a
The text was updated successfully, but these errors were encountered:
anniehedgpeth
changed the title
Ensure all variables from Settings module exists in all 3 TFE modules
Ensure all variables from Settings module exist in all 3 TFE modules
Nov 14, 2022
What problem would you like to address?
There are variables that exist in the
settings
module that are not available as variables in the TFE modules (Azure, AWS, GCP). One example isforce_tls
. Please audit the TFE modules' rootvariables.tf
andmain.tf
to ensure that every variable that is available in thesettings
module of this repository is available to configure in each of the TFE modules.Who is the audience for this request?
Everyone because everyone who uses the golden-path modules is affected by this.
What would the ideal solution look like?
Every variable in this
settings
module is available for configuration in the three TFE golden path modules.What alternatives have you considered?
n/a
How does this impact you?
As a TFE engineer, I am not able to change certain settings for test/dev environments without branching off of the TFE modules' default branch. This also means, however, that tests are not able to configure these settings.
Are there any deadlines?
no
Is there any additional context?
n/a
The text was updated successfully, but these errors were encountered: