bicep-style-guide

To enforce Bicep coding standards, apply a style guide that checks naming conventions, file layout, and decorator usage. This standardizes resource configuration and parameters to improve readability and maintainability in Azure infrastructure as code.

Bicep best practices for file layout include standardizing content order for clarity, enforcing consistent naming for resources and parameters, and requiring descriptive comments for complex expressions to ensure predictability and maintainability.

Yes, prior Bicep knowledge is required to use a Bicep style guide effectively. The guide targets developers writing Bicep scripts for cloud deployment and focuses on enforcing rules for modular design, parameter constraints, and resource tagging.

To prevent common Bicep code errors in pull requests, establish PR rejection criteria based on style guide rules. This ensures robust parameter design with default values, proper decorator validation, and consistent resource tagging before submission.

Use decorators and parameter constraints in Bicep modules to validate inputs and maintain security. A style guide encourages using decorators for robust parameter interfaces, ensuring modular and self-documenting code that reduces deployment errors.