Added -NoVersionCheck option to Connect-PnPOnline #28
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Type
Related Issues?
N/A
What is in this Pull Request ?
Added
-NoVersionChecktoConnect-PnPOnlinewhich allows for the validation of a newer version to be bypassed. Could be used i.e. in an automated process to not waste resources on doing the version check as nobody will see it anyway. Other useful scenario would be if you want to target a specific PnP PowerShell version for whatever reason and don't want to confuse the end user by seeing an instruction to upgrade while this upgrading should not be done. If the flag is not provided, the version check will still be done, so it's totally optional.