fix: replace hardcoded fixture fallback with fail-fast :? syntax#8606
Merged
Conversation
The 4 Tier 1 scenarios that copy fixtures used a hardcoded /mnt/c/Repos/... fallback path (Travis's machine). Replace with bash :? expansion so that missing AZD_AGENTS_FIXTURES fails immediately with a clear message instead of a cryptic 'No such file or directory'. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Replaces the hardcoded
/mnt/c/Repos/azure-dev/...fallback in 4 Tier 1 scenario pre-hooks with bash:?expansion.Before: If
AZD_AGENTS_FIXTURESis unset,cpsilently tries Travis's local path → cryptic 'No such file or directory'.After: Shell immediately errors with: 'Set AZD_AGENTS_FIXTURES to the WSL path of your fixtures directory' — fail-fast, clear message.
Files changed:
10-init-deploy-mode-code.yaml10-init-deploy-mode-container.yaml10-init-from-code.yaml10-init-validate-deploy-mode.yaml