feat: Enable Resource Group Reuse via Environment and RG Name Parameters

[Prasanjeet-Microsoft]

Purpose

• This PR introduces the ability to reuse existing Azure Resource Groups when deploying infrastructure using Bicep. The key updates include:

  • Added $environmentName and $resourceGroupName as new parameters.
  • Modified deployment logic to skip creation of the resource group if it already exists.
  • Ensured all resources are deployed within the provided resource group.
  • Validated that no duplicate or conflicting resources are created during test deployment.

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:

• Validate deployment succeeds when using an existing Resource Group.
• Confirm no duplicate or conflicting resources are created.
• Ensure parameters environmentName and resourceGroupName are handled correctly in both script and templates.
• Please restart the AKS (Kubernetes) service after deployment when deploying resources into an existing (reused) Resource Group to apply changes.

[github-actions]

🎉 This PR is included in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀