fix: Add required_providers to main module #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add missing
required_provider
in the main module to resolve the warning mentioned in #3 and #10.Motivation and Context
It solves an
init
warning that was put in place as part of backwards compatibility in Terraform 0.13, as explained by HashiCorp developer here. The version constraint was copied from therequired_versions
found in all the submodules' versions.tf files.Breaking Changes
It should not be a breaking change. The main module already requires Terraform
>= 1.0
and the warning was added in v0.13.How Has This Been Tested?
After receiving the warning running
terraform init -backend=false
I edited .terraform/modules/network_firewall/versions.tf and added the change and then reran the init command to confirm the warning is no longer displayed.