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
277 stars 61 forks source link

[Question/Feedback]: Required Outputs in two places #999

Open cshea-msft opened 1 month ago

cshea-msft commented 1 month ago

Check for previous/existing GitHub issues

Description

There is MUST Outputs in the Shared Specs https://azure.github.io/Azure-Verified-Modules/specs/shared/#id-rmfr7---category-outputs---minimum-required-outputs guidance doc and also in the Terraform https://azure.github.io/Azure-Verified-Modules/specs/terraform/#id-tffr2---category-outputs---additional-terraform-outputs.

Do we need both Output docs?

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.

matebarabas commented 1 month ago

@Azure/avm-core-team-technical-terraform, can you please comment on how (if?) the TF specific requirement adds more to what is already defined in the language agnostic spec as called out by @cshea-msft. Thanks!

matt-FFFFFF commented 1 week ago

Hi @cshea-msft

We are working on a PR to clarify. However there will be differences between outputs for bicep and tf due to the nature of the two languages.