About This Page
This page is part of the Azure documentation. It contains code examples and configuration instructions for working with Azure services.
Bias Analysis
Bias Types:
⚠️
windows_first
⚠️
powershell_heavy
Summary:
The documentation provides both Bash and PowerShell examples for all Azure CLI commands, ensuring parity in command-line instructions. However, in the 'Send requests' section, the Bash example uses standard Linux tools (seq, xargs, curl) with detailed explanations and links to Linux man pages, while the PowerShell example uses a more complex, Windows-specific approach (runspaces, Invoke-WebRequest) with less explanation and no cross-platform alternatives. Additionally, the instructions for opening a new shell are phrased as 'Open a new bash shell' for Bash and 'Open a new command prompt and enter PowerShell' for PowerShell, subtly placing Windows/PowerShell as a primary environment. The Bash examples are generally presented before PowerShell, but the overall structure and explanations are balanced. There are no missing Linux examples, but the PowerShell approach is more elaborate and may suggest a Windows-centric workflow for users unfamiliar with Linux tools.
Recommendations:
- In the 'Send requests' section, provide a cross-platform alternative for Windows users who may not have PowerShell (e.g., using WSL or Git Bash on Windows, or suggesting curl in Command Prompt if available).
- For the PowerShell example, consider simplifying the approach or explaining why such complexity (runspaces) is needed compared to the straightforward Bash pipeline.
- Add a note clarifying that Bash examples work on Linux, macOS, and Windows (with WSL or Git Bash), and that PowerShell Core is available cross-platform.
- Where possible, provide links to PowerShell documentation similar to the links provided for Linux tools.
- Ensure that the order of presentation does not implicitly prioritize Windows/PowerShell over Linux/Bash, or vice versa—consider alternating or explicitly stating parity.
Create pull request
Flagged Code Snippets
az containerapp up `
--name my-container-app `
--resource-group my-container-apps `
--location centralus `
--environment my-container-apps `
--image mcr.microsoft.com/dotnet/samples:aspnetapp `
--target-port 8080 `
--ingress external `
--query properties.configuration.ingress.fqdn `
az containerapp update `
--name my-container-app `
--resource-group my-container-apps `
--min-replicas 1 `
--max-replicas 10 `
--scale-rule-name my-cpu-scale-rule `
--scale-rule-type cpu `
--scale-rule-metadata type=Utilization value=<UTILIZATION>
az containerapp update `
--name my-container-app `
--resource-group my-container-apps `
--min-replicas 1 `
--max-replicas 10 `
--scale-rule-name my-http-scale-rule `
--scale-rule-http-concurrency 1
az containerapp logs show `
--name my-container-app `
--resource-group my-container-apps `
--type=system `
--follow=true
$url="<YOUR_CONTAINER_APP_FQDN>"
$Runspace = [runspacefactory]::CreateRunspacePool(1,10)
$Runspace.Open()
1..50 | % {
$ps = [powershell]::Create()
$ps.RunspacePool = $Runspace
[void]$ps.AddCommand("Invoke-WebRequest").AddParameter("UseBasicParsing",$true).AddParameter("Uri",$url)
[void]$ps.BeginInvoke()
}
az containerapp update `
--name my-container-app `
--resource-group my-container-apps `
--min-replicas 1 `
--max-replicas 10 `
--scale-rule-name my-memory-scale-rule `
--scale-rule-type memory `
--scale-rule-metadata type=Utilization value=<UTILIZATION>
az containerapp show `
--name my-container-app `
--resource-group my-container-apps `
--output yaml > app.yaml
az containerapp update `
--name my-container-app `
--resource-group my-container-apps `
--yaml app.yaml