fix: win_psDscAdapter targeted module cache refreshes #787
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
Fixes #745 by ensuring a full
Get-DscResourcerefresh is triggered when$env:PSModulePathchanges.Also reorders the cache staleness checks to prioritize detecting
PSModulePathdifferences before evaluating stale resource entries.Fixes #807 by ensuring a full cache refresh is triggered when cache is cold. It now builds a list
$namedModuleswhich determines whether targeted module refresh occurs, using this list if it does.PR Context
When
$env:PSModulePathchanges, the cache may be rebuilt incorrectly if$Moduleremains set. The module environment may have changed outside the scope defined by$Module, but the refresh will only consider the provided modules.When a module is deleted, the stale entries check will detect the change and initiate a cache refresh, skipping the check for stale paths. If the removed module is not in
$Module, the stale entries get captured in$existingDscResourceCacheEntriesand remain in the refreshed cache.A change in
PSModulePathshould result in a full cache refresh and take priority over stale resource entries.