-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat(tests): Added tests for the tfe block #96
Conversation
role_definitions.tf
Outdated
@@ -3,7 +3,7 @@ resource "azurerm_role_definition" "user_created" { | |||
role_definition_id = each.value.role_definition_id | |||
name = each.value.name | |||
description = each.value.description | |||
scope = each.value.scope | |||
scope = each.value.scope == null ? "/subscriptions/${data.azurerm_client_config.current.subscription_id}" : each.value.scope |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to discuss if we can set the default scope to the workload's resource group id. Are there any downsides to doing that @SanderBlom?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It would probably be a better to reduce the scope to the workload resource group. I'll update the PR :)
I reached out to Hashicorp about this issue and this was the response I got back: I completely understand your limitation, and we are working on enhancing how variables are done in the test framework. It might not happen asap, might be a few months, but we know this is a problem and intend on building the capability. Please open a github issue and we will prioritize this. We intend on making many more changes to the test framework, so we will work on this for sure. Omar Ismail |
I have now opened an issue on this hashicorp/terraform#34534 |
…d run restrictions
… is automatically validated in terraform 1.6
…between e2e tests
This PR resolves issue #90.
Whats has changed/added in this PR
workspace_env_vars
in the TFE block. When the module was trying to merge the variables for the TFC workspace, it was incorrectly attempting to merge content from an undefined variablevar.tfe.env_vars
.test
folder) to start withtest_
tests
folder. See new readme on how to run the test