PowerShell / PowerShell/PSResourceGet

ScriptsToProcess property must be valid before being able to update

Open
#492 5 comments 0 reactions 1 assignee View on GitHub

@anamnavi is already working on this.

Since Dec 10, 2024.

Area-InfoFile Issue-Bug
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

If my current module manifest includes a ScriptsToProcess property with invalid values (i.e. files that do not exist), I cannot update it using Update-ModuleManifest. An exception is thrown.

For example, the below may be the current value for ScriptsToProcess in my module manifest, and the referenced files do not exist.

...
ScriptsToProcess = '.\ScriptsToProcess\I-DoNotExist.ps1', 'ScriptsToProcess\I-AlsoDoNotExist.ps1'
...

I think it would be ideal to allow the user to replace the existing values, even if they're not valid.

PS C:\> Update-ModuleManifest -Path .\mymodulemanifest.psd1 -ScriptsToProcess '.\SomeScript.ps1'

Update-ModuleManifest: Cannot update the manifest properly. 'The member 'ScriptsToProcess' in the module manifest is not valid: Cannot find path 'C:\git\PSCMContentMgmt\build\PSCMContentMgmt\.\ScriptsToProcess\Import-CMModule.ps1' because it does not exist.. Verify that a valid value is specified for this field in the 'C:\git\PSCMContentMgmt\build\PSCMContentMgmt\PSCMContentMgmt.psd1' file.'
PS C:\> get-command Update-ModuleManifest

CommandType     Name                                               Version    Source
-----------     ----                                               -------    ------
Function        Update-ModuleManifest                              2.2.4.1    PowerShellGet

PS C:\> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.19041
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.