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

Request to Update for azurerm 4.0 Support #593

Open
marciobarbato opened this issue Jan 27, 2025 · 3 comments · Fixed by #594
Open

Request to Update for azurerm 4.0 Support #593

marciobarbato opened this issue Jan 27, 2025 · 3 comments · Fixed by #594

Comments

@marciobarbato
Copy link

Hi team,

First off, thanks so much for this amazing tool! It's been incredibly useful.

I’m currently trying to run an export, but I’ve encountered an issue when using azurerm version 4.16. The export fails due to a deprecated property that was removed in azurerm 4.0.

Command:

aztfexport rg --append --provider-version 4.16.0 --backend-type=azurerm --provider-name azurerm CI-USSC01-PAAS-VNET-10.68.152.0_21

Error:

10 errors occurred: 
  * task handler error: failed to merge state file: 1 error occurred:
  * showing state file /var/folders/yy/ylsnbtxn23qbz3f9wffb_2n80000gn/T/1682278556/terraform.tfstate: exit status 1
  Failed to marshal state to json: unsupported attribute "disable_bgp_route_propagation"

According to the [azurerm 4.0 upgrade guide](https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/4.0-upgrade-guide#azurerm_route_table), the disable_bgp_route_propagation property has been deprecated and removed in favor of the bgp_route_propagation_enabled property.

Would it be possible to update the tool to support azurerm 4.0 and account for this change?

Thanks again !

@xianlin
Copy link

xianlin commented Jan 28, 2025

I ran into the same issue with v4.0 of azurerm, really appreciate this support feature.

@stemaMSFT
Copy link
Member

@magodo can you confirm this has been fixed?

@stemaMSFT stemaMSFT reopened this Jan 28, 2025
@magodo
Copy link
Collaborator

magodo commented Jan 28, 2025

@xianlin I've locally tested to export a azurerm_route_table with aztfexport v0.16.0, which by default uses the azurerm v4.16.0.

By seeing you are using --append, may I ask if your existing state file is generated from a v3 azurerm provider? If that is the case, you shall stick on that provider version by using --provider-version <ver>.

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

Successfully merging a pull request may close this issue.

4 participants