Skip to content
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

Add -Force parameter to: Update-PSModuleManifest #1747

Open
iRon7 opened this issue Nov 2, 2024 · 0 comments
Open

Add -Force parameter to: Update-PSModuleManifest #1747

iRon7 opened this issue Nov 2, 2024 · 0 comments
Labels
feature_request Issue-Discussion Place for discussion about issue/feature/etc

Comments

@iRon7
Copy link

iRon7 commented Nov 2, 2024

Summary of the new feature / enhancement

In case the manifest doesn't (yet) exist, I would like to be able to create it with a single command.
Currently the Update-PSModuleManifest generates an error if the manifest doesn't yet exist:

Update-PSModuleManifest: Cannot find path '.\Test.psd1' because it does not exist.

Rather than doing something like:

if (Test-Path .\Test.psd1) { Update-PSModuleManifest -Path .\Test.psd1 @Settings }
else { New-ModuleManifest -Path .\Test.psd1 @Settings }

Proposed technical implementation details (optional)

I would like to simply do:

Update-PSModuleManifest -Path .\Test.psd1 @Settings -Force
@SydneyhSmith SydneyhSmith added Issue-Discussion Place for discussion about issue/feature/etc and removed Needs-Triage labels Nov 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature_request Issue-Discussion Place for discussion about issue/feature/etc
Projects
None yet
Development

No branches or pull requests

2 participants