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

Upgrade es-caf azurerm provider from 3.116.0 to 4.0.0 #1157

Closed
MrKeithM opened this issue Oct 16, 2024 · 3 comments
Closed

Upgrade es-caf azurerm provider from 3.116.0 to 4.0.0 #1157

MrKeithM opened this issue Oct 16, 2024 · 3 comments

Comments

@MrKeithM
Copy link

MrKeithM commented Oct 16, 2024

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

Versions

terraform: hashicorp/ - version = "3.116.0"

azure provider: azurerm

module:

Description

Im trying to upgrade the azurerm provider in my es-caf-module from version from "3.116.0" to "4.0.0" when the plan runs I get this error:


│ Error: Unsupported argument

│ on .terraform/modules/enterprise_scale/resources.connectivity.tf line 58, in resource "azurerm_subnet" "connectivity":
│ 58: private_endpoint_network_policies_enabled = each.value.template.private_endpoint_network_policies_enabled

│ An argument named "private_endpoint_network_policies_enabled" is not
│ expected here.

this error is based on a file on the resources.connectivity.tf file within the >>> .terraform/modules/enterprise_scale/resources.connectivity.tf fileany changes to this doesnt seem to be picked up. I have commented it out with no good results.

Steps to Reproduce

  1. upgrade hashicorp/azurerm version from version "3.116.0" to version "4.0.0"
  2. error should show up on the planning section citing an unrecognised arguement

Screenshots

Additional context

@kewalaka
Copy link

This is a duplicate of #1123

As noted on that issue, support for AzureRM v4 is currently targetted for v7 of this module.

@MrKeithM
Copy link
Author

This is a duplicate of #1123

As noted on that issue, support for AzureRM v4 is currently targetted for v7 of this module.

apoligies for the duplicate question, will track the updates on the referenced issue 👍🏾

@matt-FFFFFF
Copy link
Member

CLosing as dupe

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

No branches or pull requests

3 participants