microsoft-github-policy-service[bot]
commented
6 days 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.
matebarabas
Check for previous/existing GitHub issues
Description
Currently .NET Aspire supports provisioning Azure resources for development-time usage: https://github.com/dotnet/aspire/tree/main/src/Aspire.Hosting.Azure
You create Bicep files like you normally do, inject params & use the outputs. For secrets you can employ some secret sauce where you add a Key Vault Secret within your Bicep and Aspire creates a Vault and stuffs it in there so you don't risk checking in things you shouldn't.
As it's plain Bicep you can of course add Verified Modules as you see fit within, but that's outside Aspire's scope. For deployment-time you're driven towards using the Azure Developer CLI. (Which isn't using AVM either, but that's a separate thread: https://github.com/Azure/azure-dev/issues/2386)
I think it would be useful to be able to skip straight to consuming modules from Aspire code like
var foo = builder.AddBicepVerifiedModule(...)On a technical level it would probably be useful to support modules in a generic way, but after all this is the AVM repo :)
Does this make sense or should it be filed over in the Aspire repo instead? Or is it a matter of "if the community wants it; build it"?