6180b59e87
- Remove the `Default` value for the `configuration` parameter in the `README.md` file - Make the `configuration` parameter optional in the `main.bicep` file - Update the `defaultValue` property of the `configuration` parameter to `null` in the `main.json` file |
||
|---|---|---|
| .devcontainer | ||
| .github | ||
| .vscode | ||
| avm | ||
| modules | ||
| .editorconfig | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .prettierignore | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| SUPPORT.md | ||
| bicepconfig.json | ||
| package-lock.json | ||
| package.json | ||
README.md
⚠️ New standard for Bicep modules - AVM ⚠️
To provide our customers with a unified experience, Azure Verified Modules (AVM) is now the single Microsoft standard for Bicep modules, published to the Public Bicep Registry, via this repository.
[!IMPORTANT] Going forward, new modules need to be developed and published in accordance with the AVM specifications. Module proposals for new, non-AVM modules are no longer accepted. To propose a new AVM module, you can file an AVM Module Proposal.
Existing non-AVM modules have been retired or migrated to AVM. To provide continued access for existing customers, non-AVM modules formerly published in the registry will be kept there indefinitely, but their source code has been replaced with an informational notice and a pointer to their successor in AVM, when applicable. Visual Studio Code IntelliSense support for the old, non-AVM modules have also been removed - while existing references will keep working.
For the list of available and planned AVM modules, please visit the AVM Module Index pages.
Bicep Registry Modules
This repo contains the source code of all currently available Bicep modules in the Bicep public module registry (i.e., all AVM Bicep modules).
Available Modules
To view all available AVM Bicep modules, go to AVM Bicep Module Index (https://aka.ms/AVM/ModuleIndex/Bicep).
Contributing
Only Microsoft employees can be module owners at this time. Teams within Microsoft can refer to AVM Bicep Contribution Guide for information on contributing modules.
External customers can propose new modules via AVM Module Proposals, submit feature requests or report bugs via AVM Module Issues and can also contribute to modules via working with a Microsoft module owner.
Data Collection
The software may collect information about you and your use of the software and send it to Microsoft. Microsoft may use this information to provide services and improve our products and services. You may turn off the telemetry as described in the repository. There are also some features in the software that may enable you and Microsoft to collect data from users of your applications. If you use these features, you must comply with applicable law, including providing appropriate notices to users of your applications together with a copy of Microsoft’s privacy statement. Our privacy statement is located at https://go.microsoft.com/fwlink/?LinkID=824704. You can learn more about data collection and use in the help documentation and our privacy statement. Your use of the software operates as your consent to these practices.