Test computed file auto merge

[ouldsid]

PR Checklist

Check these items before submitting a PR...

Contribution Guide

Best Practice Guide

• - Please check this box once you've submitted the PR if you've read through the Contribution Guide and best practices checklist.

Changelog

[ouldsid]

/validate

[github-actions]

🤖 Quickstart Sample Summary

Sample Summary

• This sample deploys an Azure deployment script resource that demonstrates best practices for passing and reading complex inputs, outputs, and logs using an Azure CLI deployment script.

• The deployment script runs a shell script with inputs of various types (boolean, integer, string, array, object) and provides corresponding outputs and logs.

• The sample showcases handling of complex parameter types in deployment scripts and how to consume their outputs.

• To deploy this sample, provide parameter values for boolean, integer, string, array, and object inputs as defined in the template.

• Deployment can be done via the Azure portal or CLI, as it uses a single main Bicep template.

Resources Deployed

• Microsoft.Resources/deploymentScripts (from main.bicep): Deploys an Azure CLI deployment script resource named myScript. This script runs a shell script (content loaded from script.sh) with argument passing.
• Microsoft.Resources/deploymentScripts/logs (from main.bicep): References the default logs sub-resource of the deployment script, enabling retrieval of the logs produced by the script during execution.

Security Findings

• No security issues detected by MSDO scanners (Template Analyzer, Checkov, Trivy, Terrascan).
• No hardcoded secrets or overly permissive access were found in the template.

Key Parameters

• myBool (bool): An example boolean input parameter.
• myInt (int): An example integer input parameter.
• myString (string): An example string input parameter.
• myArray (array): An example array input parameter.
• myObject (object): An example object input parameter.

Notes for Reviewers

• The template reads script content from a local file script.sh which is referenced but not shown in the PR — its presence and content should be confirmed during deployment.
• The deployment script uses AzureCLI kind with a specified azCliVersion of 2.50.0.
• No changes in resource types or significant logic were introduced, only minor description edits.
• Parameters and outputs are clearly documented with descriptions.
• No security-sensitive patterns were observed.

Files Touched

• main.bicep
• metadata.json

---

Generated by the quickstart summarizer agent (v2 — agentic + MSDO security) · triggered by /validate