docs: updated the env step in deployment guide readme #538
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 deployment guide to clarify the process of configuring your environment, especially regarding the generation and location of the
.envfile when using Azure Developer CLI (azd). The instructions now account for scenarios where resources are provisioned withazd, making the setup process clearer for users.Deployment documentation improvements:
docs/DeploymentGuide.mdto explain that if resources are provisioned usingazd provisionorazd up, the.envfile is automatically generated in the.azure/<env-name>/.envdirectory, and provided guidance on how to determine the current environment name usingazd env list.APP_ENVis set to "dev" in their.envfile, regardless of how the file was created.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information