Giters

Azure / Azure-Verified-Modules

Azure Verified Modules (AVM) is an initiative to consolidate and set the standards for what a good Infrastructure-as-Code module looks like. Modules will then align to these standards, across languages (Bicep, Terraform etc.) and will then be classified as AVMs and available from their respective language specific registries.

Home Page:https://aka.ms/AVM

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Question/Feedback]: How do we change the MI for the e2e testing workflow?

ibersanoMS opened this issue · comments

commented

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Description

I updated the client_id, subscription_id, and tenant_id in the test environment for my module , but it keeps failing because it's still using an old MI with the previous owner's subscription. I see there's an environment variable MSI_ID being used, but I don't see where it's initialized/set.

commented

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the AVM Issue Triage documentation.

Note

This label was added as per ITA06.

commented

@Azure/avm-core-team-technical-terraform, please take a look. Thanks!

commented

@matt-FFFFFF could you advise on this

commented

Hi,

Why do you want to change the MSI? It is intrinsic to the Azure resource running the test.

The test environment is deliberately isolated as a security measure.