What runs Bicep deployments automatically when code merges?
Why D is the answer
A GitHub Actions workflow
A GitHub Actions workflow can run on merge and deploy Bicep templates, so nobody runs them by hand.
In detail
- A GitHub Actions workflow runs on merge, and deploys the templates.
- Use environments and approvals for production.
Use case
An illustrative scenario, not a real incident.
On merge, a GitHub Actions workflow deploys the Bicep templates, so nobody runs them by hand.
See it in different ways
flowchart LR A["Bicep in Git"] --> B["GitHub Actions"] B --> C["Dev workspace"] B --> D["Test workspace"] B --> E["Prod workspace"]
sequenceDiagram participant D as Developer participant G as GitHub participant A as GitHub Actions participant Z as Azure D->>G: Merges a Bicep change G->>A: Starts the workflow A->>Z: Signs in with OpenID Connect A->>Z: Deploys to dev, test and prod
flowchart LR S0["Merge"] --> S1["GitHub Actions"] --> S2["Sign in to Azure"] --> S3["Deploy Bicep"]
Key point: Workflows deploy on merge.
Why the other options are wrong
- A. A notebook cell run by hand on one developer's machine
- A notebook cell is run by hand.
- B. An MLflow experiment logged to the workspace
- An experiment records runs.
- C. A scoring script deployed to a managed endpoint
- A scoring script serves predictions.