fix: Short-circuit adapter discovery when a native resource type has no matching version#1532
Draft
Gijsreyn wants to merge 1 commit into
Draft
Conversation
…no matching version
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.
PR Summary
This pull request makes discovery fail fast in a scenario when a configuration document pins a resource with
requireVersion,and the requested type is a known native command-based DSC resource, but no installed version satisfies the requirement.When a user adds the
requireAdapterin the configuration document, a sweep still runs, so that behavior is unchanged. It is mainly on native type + version mismatch + norequireAdapter.PR Context
Fixes #1531