You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a draft powershell script that called the following in the begin{} block: Set-ConfluenceInfo -BaseURi "$baseUri" -Credential $ConfluenceCredential
Then in the process{} block I would use Get-ConfluencePage and Set-ConfluencePage with the following parameters: Get-ConfluencePage -SpaceKey $SpaceKey | Where-Object {$_.Title -eq $PageTitle}
Once I was happy with the script I created a function around it and added to a module but it would always ask me for the ApiUrl when Get-ConfluencePage was called.
I temporary workaround was to add the following when wrapping as a function
I created a draft powershell script that called the following in the
begin{}
block:Set-ConfluenceInfo -BaseURi "$baseUri" -Credential $ConfluenceCredential
Then in the
process{}
block I would use Get-ConfluencePage and Set-ConfluencePage with the following parameters:Get-ConfluencePage -SpaceKey $SpaceKey | Where-Object {$_.Title -eq $PageTitle}
Once I was happy with the script I created a function around it and added to a module but it would always ask me for the
ApiUrl
when Get-ConfluencePage was called.I temporary workaround was to add the following when wrapping as a function
Is there a known issue for why the behaviour is different and incompatible when called as a function instead of script?
The text was updated successfully, but these errors were encountered: