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

Deprecated method for pinning provider versions #196

Closed
bbchase opened this issue Feb 17, 2022 · 1 comment · Fixed by #237
Closed

Deprecated method for pinning provider versions #196

bbchase opened this issue Feb 17, 2022 · 1 comment · Fixed by #237

Comments

@bbchase
Copy link

bbchase commented Feb 17, 2022

The using-terraform-modules.md doc suggests pinning the provider version in the provider block, but this method is deprecated. Provider version constraints should now be in the required_providers block. (See line 42)

The service catalogue has already been updated (e.g. vpc-app, which is used as the example for this doc), but the docs themselves appear to be out of date.

terraform warning message:

Warning: Version constraints inside provider configuration blocks are deprecated

  on provider.tf line 5, in provider "aws":
   5:   version = "~> 3.0"

Terraform 0.13 and earlier allowed provider version constraints inside the
provider configuration block, but that is now deprecated and will be removed
in a future version of Terraform. To silence this warning, move the provider
version constraint into the required_providers block.
@eak12913
Copy link
Contributor

Thanks @bbchase for the submission and my apologies that this took so long for us to get to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants