fix: Added createdBy tag in resourcedeployment.ps1 file

[NirajC-Microsoft]

Purpose

This pull request adds support for tracking and tagging Azure resource deployments with the user who initiated the deployment, improving traceability and auditability. The changes ensure that a createdBy tag is consistently set during resource group creation, updates, and deployments, and that this information is passed through from the deployment scripts to the Bicep templates.

Tagging and parameterization improvements:

• Added a createdBy parameter to main.bicep, allowing the user name of the deployer to be passed in and used as a resource group tag, replacing the previous hardcoded extraction from the deployer principal name.
• Updated resource group creation, update, and deployment commands in resourcedeployment.ps1 to set the createdBy tag using the provided email or pipeline context, ensuring consistent tagging for all resource groups. [1] [2] [3]
• Added an output for createdBy in main.bicep to expose the value used during deployment.

Deployment script enhancements:

• Modified the deployment PowerShell script to determine the createdBy value based on whether the deployment is running in CI or interactively, improving automation and user attribution.

Minor script and parameter fixes:

• Added a missing comma in the PowerShell function parameter list and fixed formatting in the Azure login command. [1] [2]
• ...

Does this introduce a breaking change?

• Yes
• No

Golden Path Validation

• I have tested the primary workflows (the "golden path") to ensure they function correctly without errors.

Deployment Validation

• I have validated the deployment process successfully and all services are running as expected with this change.

What to Check

Verify that the following are valid

• ...

Other Information

[github-actions]

🎉 This PR is included in version 1.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀