Fix AzureCLI@2 fallback when 'az version' returns empty output #21518
+2
−2
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.
Fixes #21512
When the UseAzVersion feature flag is enabled, the AzureCLI@2 task runs 'az version' instead of 'az --version'. In some environments, 'az version' returns exit code 0 but with empty stdout, causing the version parsing to fail.
The existing fallback logic only checked for non-zero exit codes or stderr output, but didn't handle the case where stdout is empty or contains only whitespace.
This fix adds checks for empty stdout to trigger the fallback to 'az --version', ensuring the task works reliably.