search

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.
https://aka.ms/AVM
MIT License
282 stars 61 forks source link

[Feature Request]: Align and document identity feature across modules #991

Open eriqua opened 1 year ago

eriqua commented 1 year ago

Description

The identity feature should be aligned across all modules supporting it (parameters, variables, resource setting and outputs naming and implementation).

A dedicated paragraph should be added to the module design patterns section.

rahalan commented 1 year ago

Compare implementations and decide for best one, before implementing for all modules

AlexanderSehr commented 9 months ago

Should align to AVM specs

AlexanderSehr commented 1 month ago

Hey @eriqua, I wonder what to do with this. I guess each spec in AVM should justify why something is done a certain way (which I doubt it is). Do you think it would make sense to transition it to the AVM repository?

eriqua commented 1 month ago

@AlexanderSehr I agree, it's probably one to move to AVM repo, documentation related, rather than BRM, since the implementation 'should' already be aligned

AlexanderSehr commented 1 month ago

Alright, will transfer it then. Let's see if anybody picks it up 😉

microsoft-github-policy-service[bot] commented 1 month ago

[!IMPORTANT] The "Needs: Triage :mag:" 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.