You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
// =============== //// Definitions //// =============== //
@export()
typesecretSetType = {
@description('The resourceId of the exported secret.')
secretResourceId: string
@description('The secret URI of the exported secret.')
secretUri: string
}
typesecretToSetType = {
@description('Required. The name of the secret to set.')
name: string
@description('Required. The value of the secret to set.')
@secure()
value: string
}
The text was updated successfully, but these errors were encountered:
Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.
Tip
To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!
Hey @seesharprun & @bryansan-msft,
Please triage the issue when you get the chance.
From where I'm standing it makes sense and is a very quick update 🙂
Hey @dciborow,
please excuse the late reply. The automatic owner-assignment did not kick in as the issue was not created as a module issue. Highly recommend for the future 😉
The CosmosDB template can use type parameters that could be imported by users to make it easier to use.
https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/document-db/database-account/main.bicep
Example of how it is done in the mongo db template.
bicep-registry-modules/avm/res/document-db/mongo-cluster/modules/keyVaultExport.bicep
Line 30 in a237334
The text was updated successfully, but these errors were encountered: