Remove pipeline variables section from azure.yaml per azd 1.17.0+ #262
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.
As of Azure Developer CLI version 1.17.0, the
pipeline:
variables:
section inazure.yaml
is no longer needed. The Azure Developer CLI now auto-detects required variables frommain.parameters.json
.This PR updates the repository's
azure.yaml
by:pipeline:
block (23 lines) including all nestedvariables:
entries">= 1.10.0"
to">= 1.17.0"
to enforce the modern azd version0.0.1
to0.0.2
to indicate the changeBenefits:
Validation:
infra/main.parameters.json
The two variables not found in
main.parameters.json
(AZURE_OPENAI_VERSION
andAZURE_OPENAI_EMBEDDING_COLUMN
) appear to be legacy/unused, confirming that the auto-detection approach is sufficient.Fixes #261.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.