Bias Analysis
Detected Bias Types
windows_first
powershell_heavy
Summary
The documentation provides both Azure CLI and Azure PowerShell examples for deploying and cleaning up Bicep resources. However, PowerShell (a Windows-centric tool) is given equal prominence as Azure CLI, and Visual Studio Code is the only editor mentioned for Bicep development. There is no explicit mention of Linux-specific tools, shell environments, or editor alternatives. The examples and instructions do not reference Linux shell patterns (e.g., bash, zsh), nor do they address platform-specific nuances for Linux users.
Recommendations
- Explicitly mention that Azure CLI commands work on Linux, macOS, and Windows, and provide bash/zsh syntax for variable assignment (e.g., resourceGroupName="value") instead of PowerShell-style ($resourceGroupName).
- Include instructions or examples for deploying Bicep files using bash or other Linux-native shells, clarifying any differences in command syntax or environment setup.
- List alternative editors for Bicep development, such as Vim, Emacs, or JetBrains IDEs, and note their cross-platform availability.
- Add a note or section addressing Linux/macOS users, including any prerequisites or installation steps that differ from Windows.
- Ensure that CLI examples precede PowerShell examples, or clarify that CLI is cross-platform while PowerShell is primarily Windows-focused.
Create Pull Request