upgrade azurerm to latest version

[Adam-D-Lewis]

Reference Issues or PRs

Fixes #2806

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

How to test this PR?

Any other comments?

[marcelovilla]

This looks good but I wanted to confirm everything works as expected by running our Azure tests from this branch: https://github.com/nebari-dev/nebari/actions/runs/11628815929

Unfortunately, they failed because of a Vault issue, completely unrelated to this PR. Once we have fixed that, I'll re-trigger them and see if the deployment works in Azure.

[Adam-D-Lewis]

Thanks Marcelo, I haven't tested it yet.

[marcelovilla]

@Adam-D-Lewis I re-triggered the Azure deployment workflow now that Vault is working again and found another issue when it tries logging-in: https://github.com/nebari-dev/nebari/actions/runs/11628815929/job/32469625611#step:6:33

Running Azure CLI Login.
/usr/bin/az cloud set -n azurecloud
Done setting cloud: "azurecloud"
Federated token details:
 issuer - https://token.actions.githubusercontent.com/
 subject claim - repo:nebari-dev/nebari:ref:refs/heads/upgrade_azurerm_provider
Attempting Azure CLI login by using OIDC...
Error: AADSTS700213: No matching federated identity record found for presented assertion subject 'repo:nebari-dev/nebari:ref:refs/heads/upgrade_azurerm_provider'. Please note that the matching is done using a case-sensitive comparison. Check your federated identity credential Subject, Audience and Issuer against the presented assertion. https://learn.microsoft.com/entra/workload-id/workload-identity-federation Trace ID: ea8ccd7f-2663-42b5-9130-450be9707200 Correlation ID: aaf97b77-ef83-4a2e-b225-8ebe0106d6f7 Timestamp: 2024-11-04 10:49:52Z

Error: Interactive authentication is needed. Please run:
az login

Error: Login failed with Error: The process '/usr/bin/az' failed with exit code 1. Double check if the 'auth-type' is correct. Refer to https://github.com/Azure/login#readme for more information.

Do you recognize this error?

[Adam-D-Lewis]

I'll take a look

[Adam-D-Lewis]

Sorry I put this as a draft since it's not ready for merge. I'm sure there'll need to be some adjustments made for this to deploy without error, and I haven't had a chance to do so.