Fix examples with -BearerToken parameter

[FH-Inway]

It seems that several cmdlets with a -BearerToken parameter have examples with an incorrect specification of the parameter.

For example, Invoke-D365LcsUpload has the following example:

d365fo.tools/d365fo.tools/functions/invoke-d365lcsupload.ps1

Line 96 in 5cdf57d

PS C:\> Invoke-D365LcsUpload -ProjectId 123456789 -BearerToken "Bearer JldjfafLJdfjlfsalfd..." -FilePath "C:\temp\d365fo.tools\Release-2019-05-05.zip" -FileType "SoftwareDeployablePackage" -Name "Release-2019-05-05" -Filename "Release-2019-05-05.zip" -FileDescription "Build based on sprint: SuperSprint-1" -LcsApiUri "https://lcsapi.lcs.dynamics.com"

Note the -BearerToken "Bearer JldjfafLJdfjlfsalfd..." part with the "Bearer " prefix in front of the actual token value. When executing the cmdlet in this style with valid values, this results in an error:

VERBOSE: [05:33:45][Start-LcsUploadV2] Invoke LCS request.
VERBOSE: POST https://lcsapi.lcs.dynamics.com/box/fileasset/CreateFileAsset/123456789 with -1-byte payload
[05:33:46][Start-LcsUploadV2] Error status code Forbidden in starting a new deployment in LCS. Forbidden. | The remote server returned an error: (403) Forbidden.
WARNING: [05:33:46][Start-LcsUploadV2] Stopping because of errors

If the cmdlet is called without the "Bearer " prefix, the execution is successful.

Note that there are cmdlets where the parameter is specified without the "Bearer " prefix in the examples, e.g. Get-D365LcsDatabaseBackups

d365fo.tools/d365fo.tools/functions/get-d365lcsdatabasebackups.ps1

Line 62 in 5cdf57d

PS C:\> Get-D365LcsDatabaseBackups -ProjectId 123456789 -BearerToken "JldjfafLJdfjlfsalfd..." -LcsApiUri "https://lcsapi.lcs.dynamics.com"

The cmdlets with wrong examples are:

• Invoke-D365LcsUpload
• Get-D365LcsDeploymentStatus
• Invoke-D365LcsDeployment
• Get-D365LcsEnvironmentMetadata

Internal cmdlets

• Start-LcsDeploymentV2
• Get-LcsEnvironmentHistory
• Get-LcsDeploymentStatusV2
• Complete-LcsUploadV2
• Start-LcsUploadV2
• Invoke-RequestHandler
  • Not sure about this one, it is not a parameter, but part of the -Headers parameter specification.

[Splaxi]

Good catch!