At the following line, the address to the LCS API is hardcoded to lcsapi.lcs.dynamics.com, this can trigger authentication issues for LCS projects hosted in other regions, such as Europe
|
Get-D365LcsApiToken -ClientId $settings.lcsClientId -Username "$lcsUsernameSecretname" -Password "$lcsPasswordSecretName" -LcsApiUri "https://lcsapi.lcs.dynamics.com" -Verbose | Set-D365LcsApiConfig -ProjectId $settings.lcsProjectId |
I think it's easy to solve by introducing a parameter, and having it default to lcsapi.lcs.dynamics.com. I'll submit a pull request sometime this weekend, I'm still learning how to add parameters. I also wanted to get your opinions if I'm completely wrong
At the following line, the address to the LCS API is hardcoded to lcsapi.lcs.dynamics.com, this can trigger authentication issues for LCS projects hosted in other regions, such as Europe
fscps.gh/RunPipeline/RunFSCMPipeline.ps1
Line 178 in 77827b2
I think it's easy to solve by introducing a parameter, and having it default to lcsapi.lcs.dynamics.com. I'll submit a pull request sometime this weekend, I'm still learning how to add parameters. I also wanted to get your opinions if I'm completely wrong