fix: Prevent removal of existing RG tags when deploying GSA #595
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Purpose
This pull request updates the resource group tags handling in the infrastructure templates to ensure that tags from the resource group are merged with existing tags when deploying resources. Additionally, it corrects the order of dependencies in the generated ARM template.
Tag merging improvements:
resourceGroupTagsresource inmain.bicepto merge the current resource group's tags with custom tags, ensuring all relevant tags are applied to resources.tagsproperty in the generatedmain.jsonARM template to includeresourceGroup().tagsin the merge operation, aligning the JSON output with the Bicep source.Template and dependency updates:
templateHashinmain.jsonto reflect the changes in the template.dependsOnarray for private DNS zones inmain.jsonto maintain consistency and correctness.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information