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

Ensure all variables from Settings module exist in all 3 TFE modules #93

Open
anniehedgpeth opened this issue Nov 14, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@anniehedgpeth
Copy link
Contributor

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 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

@anniehedgpeth anniehedgpeth added the enhancement New feature or request label Nov 14, 2022
@anniehedgpeth 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant