refactor: merge dev into main #539
Open
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 deployment workflows, documentation, and infrastructure configuration to improve resource tagging and enforce compatibility with the latest Azure Developer CLI (azd) version. The main changes include adding detailed resource tags during deployments, updating the required azd version to 1.18.0 or higher, and enhancing documentation to reflect these requirements.
Deployment Workflow Improvements:
.github/workflows/deploy.yml
and.github/workflows/deploy-waf.yml
to generate a current UTC timestamp and include it, along with additional metadata, in thetags
parameter when deploying resources. This ensures that each deployment is traceable with a creation date and purpose. [1] [2] [3] [4]Infrastructure Tagging Enhancements:
infra/main.bicep
to improve the handling of thecreatedBy
tag, using the user's principal name if available or falling back to the object ID, and to add aType
tag based on networking configuration.Documentation and Version Requirements:
azure.yaml
,README.md
, anddocs/DeploymentGuide.md
to require azd version 1.18.0 or higher, and added prominent notes and links to ensure users install the correct version before deploying. [1] [2] [3] [4]Does this introduce a breaking change?
How to Test