This repository has been archived by the owner on Jan 19, 2021. It is now read-only.
Get-PnPTenantTemplate: Fixing Configuration parameter not being optional and throwing exception #2873
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
Update fork
update my fork
…izing it with reasonable default value
|
Thank you! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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?
Fixes at least some of the "Object reference not set to an instance of the object" errors in #2587 (but not the original 403 error).
What is in this Pull Request ?
Fixing Configuration parameter not being optional by inititializing it with reasonable default value that is not just empty, but contains the given SiteUrl. This fixes the surprising and confusing exception one gets when omitting the parameter. See #2587 for samples of that.