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 to azurerm 3.9.0 #1400

Closed
wants to merge 32 commits into from
Closed

Upgrade to azurerm 3.9.0 #1400

wants to merge 32 commits into from

Conversation

arnaudlh
Copy link
Member

This PR is to cover upgrade to azurerm 3.9.0

@arnaudlh arnaudlh self-assigned this Oct 21, 2022
@arnaudlh arnaudlh requested a review from LaurentLesle October 21, 2022 05:16
@nusrath432
Copy link
Contributor

@arnaudlh @SergioMiyama How does this upgrade align with Rover & caf-terraform-landingzones (https://github.com/Azure/caf-terraform-landingzones) - if we could have a Roadmap / upgrade pinned up ticket / wiki it would be very helpful, please.

@bkarstaedt
Copy link
Contributor

@arnaudlh how great is the chance to upgrade azurerm to latest (3.28.0)?

For azurerm_storage_account the immutability_policy is introduced which would be great for WORM archiving scenarios...

@eoware
Copy link

eoware commented Oct 28, 2022

@arnaudlh @SergioMiyama How does this upgrade align with Rover & caf-terraform-landingzones (https://github.com/Azure/caf-terraform-landingzones) - if we could have a Roadmap / upgrade pinned up ticket / wiki it would be very helpful, please.

This would be nice to know. The current CAF starter uses Standard SKU firewalls which can't be changed to the new Basic SKU because the AzureRM version doesn't recognize the SKU.

@brk3
Copy link
Contributor

brk3 commented Nov 15, 2022

@arnaudlh @LaurentLesle Anything the community can do to help this PR along?

@MrTolerant
Copy link

MrTolerant commented Jan 10, 2023

Good day! How we can help with updating to latest azurerm?
This PR is very urgent for all!
Can spend couple of days;

@hadiulla
Copy link
Contributor

When can we expect this PR to be merged? This is becoming blocker for most of the community because of this bug - #1173

@arnaudlh
Copy link
Member Author

@MrTolerant @hadiulla @brk3 @eoware @bkarstaedt @nusrath432 thanks folks for the energy!

We are all looking forward for this update to pass! @LaurentLesle and myself are working on it in the next few days.

For the really impatient, you can follow the branch int-azrm-3.44.1 where we are polishing things up.

Roadmap:

Get 5.7.0 (this module update to azurerm 3.x) to work with all examples and with minor config file edits, and we will be assessing reasonable backport to 5.6.x of bugs we found in

Once it is out, you we can start integrating feature upgrades and augmentation.

Hope that clarifies! I will close this PR and we will open a new one on new branch in the next few days!

@arnaudlh arnaudlh closed this Feb 24, 2023
@nusrath432
Copy link
Contributor

@arnaudlh @LaurentLesle Thank you for all the hard work ... appreciate your efforts.

@arnaudlh arnaudlh deleted the int-azrm-3.7.0 branch June 14, 2023 08:03
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 this pull request may close these issues.

Error in function call - data.azurerm_client_config.current.object_id is ""
9 participants