fix: Adding a hardcoded createdBy parameter to the RAdeploy.yml file to prevent validation pipeline failures caused by the deployer function in the Bicep file. #660
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 introduces a minor enhancement to the deployment workflow and infrastructure template to improve traceability of resource creation. The main change is the addition of a
createdBy
parameter that records the pipeline or user responsible for the deployment.Parameterization and resource tagging:
.github/workflows/RAdeploy.yml
: The Azure deployment command now passes acreatedBy="Pipeline"
parameter, allowing the infrastructure to record that the deployment was initiated by the pipeline.infra/bicep/main.bicep
: Added a newcreatedBy
parameter to the Bicep template, which defaults to the deployer's username if not explicitly set. The resource group tags now use this parameter for theCreatedBy
tag, enabling better tracking of resource ownership....
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information