-
Notifications
You must be signed in to change notification settings - Fork 7
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
Two issues with Set-VenafiStandaloneScript #292
Comments
This is because that script just copies each function into your script including the signature of the function. You have to remove the signatures and make sure that the functions are in the correct place in the script before it will run. |
Thanks @Alex-Gomez-Lopez for reporting this. I recently came across the first error and you beat me to creating an issue for it. This is due to us signing the module beginning in 6.0 and including that in the updated script. As a workaround, remove the signature(s) for error 1. For the second error, that enum should have been added to the script. Perhaps it is lower in the script. I'll look into it. |
It actually includes the sigs from the enums and classes, not functions. |
This issue has been fixed and will be merged, but is no longer needed beginning with 6.5.0. The release now includes all functions merged into 1 psm1 and then signed. This new psm1 can be delivered side by side with the script and add |
After using Set-VenafiStandaloneScript to generate a VenafiPS v6.4.0-based standalone PowerShell script I have encountered these two errors:
I am not sure if these errors are caused by a bug or else there is something I am missing, thanks in advance!! Version of PowerShell is 5.1 running on Windows Server 2019 Datacenter build 17763.2061.
The text was updated successfully, but these errors were encountered: