auto generated documentation and schema #2301
-
|
Would be great if it is possible, based on parameters and variables descriptions to auto generated Documentation and Architecture schema like armviz.io |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 3 replies
-
|
Hi @Antse - can you share a bit more what you are looking for on documentation? Could you provide a code sample and the corresponding documentation you would want to see? The visualization ask makes sense and we're definitely looking to see how we can light this up. |
Beta Was this translation helpful? Give feedback.
-
|
by auto generated documentation i mean something like : (must confess i take some example from the official documentation) Code : @description('This is the storage account Name')
param stoName string
@description('This is my secure param')
@secure()
param secureParam string
resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
name: stoName // must be globally unique
location: 'eastus'
sku: {
name: 'Standard_LRS'
}
kind: 'StorageV2'
properties: {
supportsHttpsTrafficOnly: true
}
tags: {
'env':secureParam
}
}Doc : Deploy a Storage AccountOverview (global deployed resources schema)ParametersstoName
secureParam
ExamplesDeploy Bicep file to a resource groupAz CLI: az deployment group create -f ./main.bicep -g my-rgAzure PowerShell: New-AzResourceGroupDeployment -TemplateFile ./main.bicep -ResourceGroupName my-rg
Deploy with parametersOur Bicep file exposed two parameters that we can be optionally overridden ( Pass parameters on the command lineAz CLI: az deployment group create -f ./main.bicep -g my-rg --parameters secureParam=MySecretParam stoName=uniquelogstorage001Azure PowerShell: New-AzResourceGroupDeployment -TemplateFile ./main.bicep -ResourceGroupName my-rg -location westus -stoName uniquelogstorage001 -secureParam MysecretParam |
Beta Was this translation helpful? Give feedback.
-
|
Great suggestion, this would be really useful! Would you mind creating an issue to track it? IMO, the biggest challenge here will be giving users the level of customizability they want; I feel that everyone will have a slightly different expectation around how documentation should be formatted, and what information is relevant. It's also quite likely we're going to need to documentation generation capabilities as part of #62. This should be aided by #1665. |
Beta Was this translation helpful? Give feedback.

Great suggestion, this would be really useful! Would you mind creating an issue to track it?
IMO, the biggest challenge here will be giving users the level of customizability they want; I feel that everyone will have a slightly different expectation around how documentation should be formatted, and what information is relevant.
It's also quite likely we're going to need to documentation generation capabilities as part of #62.
This should be aided by #1665.