Improve Developer CLI error handling for prerequisites and Azure subscription validation #665
Conversation
This file contains 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
… and enforce App Registration on that tenant
tjementum
deleted the
pp-295-cli-fails-if-prerequisite-is-not-installed
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary & Motivation
Fix an issue in the Developer CLI where missing prerequisites (e.g., NodeJS) resulted in the CLI exiting without any error message. The CLI now correctly identifies missing prerequisites and displays an error such as:
NodeJS of minimum version 25.3.0 should be installed.Additionally, a validation has been added to the
configure-continuous-deploymentsCLI command to ensure that the selected Azure subscriptions for staging and production belong to the same tenant, preventing configuration errors.Checklist