refactor: update naming conventions for resources in Bicep files #368
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 includes significant changes to the naming conventions in multiple infrastructure files to improve consistency and readability. Additionally, it introduces post-provision hooks in the
azure.yaml
file.Naming Convention Changes:
infra/deploy_ai_foundry.bicep
: Updated various resource names to use a consistent prefix format. For example,storageName
changed from${solutionName}hubstorage
tost${solutionName}hub
, andaiServicesName
changed from${solutionName}-aiservices
toais-${solutionName}
.infra/deploy_app_service.bicep
: Modified resource names to follow the new naming convention. For instance,HostingPlanName
changed from${ solutionName }-app-service-plan
toasp-${ solutionName }
, andWebsiteName
changed from${ solutionName }-app-service
toapp-${ solutionName }
.infra/deploy_cosmos_db.bicep
: ChangedaccountName
from${ solutionName }-cosmos
tocosmos-${ solutionName }
.infra/deploy_keyvault.bicep
: UpdatedkeyvaultName
from${solutionName}-kv
tokv-${solutionName}
.infra/main.json
: Applied the new naming convention across multiple parameters and variables, such asApplicationInsightsName
,WorkspaceName
,accountName
, and more. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17]Introduction of Post-Provision Hooks:
azure.yaml
: Added post-provision hooks for both Windows and POSIX environments to display the web app URL after provisioning.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information