-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better message around prerelease modules #4024
Comments
Which additional scenarios should inform the user?
The code that does this specific check occurs outside of the core configuration component. If we wanted it to be universally available, I think the best solution would be to add new APIs to the core component and shift the current code into the processor. This would be a somewhat larger task that would really only help Improvements to the error messaging around "we couldn't find the resource" could be made more easily to just the |
I think it should be in each scenario. This is a "help the user" fall into the pit of success. It's going to be even more complex for enterprise customers with source and configuration restrictions to understand and help their users. |
In order to scope this down to get an initial improvement out, feel free to create another "smaller" issue for the CLI side, and we can work on the larger scoped improvements in the future. |
Description of the new feature / enhancement
When I have a configuration and it is attempting to use a DSC Resource in a prerelease PowerShell module, the configuration fails if I have "prerelease: false". When the configuration is being evaluated, it should help in the case where a prerelease module is available but a stable module is not.
Related to/Inspired by:
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered: