Closed megel closed 1 year ago
Nothing that I see suggests that this is an issue with the accelerator as much as an issue with the platform and or task. Unless there are more details I am missing, there's not much we can do in the accelerator to address this. If there are more details you can provide that lead you to believe this is an accelerator issue, not a platform/task issue, please do let us know. We just call the Power Platform Build Tools tasks. The repo for those tasks is here: https://github.com/microsoft/powerplatform-build-tools
However, they might end up telling you they simply call the Dataverse API and your best bet really is to contact support. To try to save you from jumping around, if there aren't more details you can give us to narrow down to an actual Accelerator issue or that it's an issue in the actual Build Tools task, I would suggest going here: https://admin.powerplatform.microsoft.com/support ...and using these options:
HTH
+1 to @devkeydet comment. The only thing I can think of, based on the error, is it's a permissions issue with the App User in the development environment.
@mikefactorial @devkeydet I just had the same thing with the Publish Customisations task on the Dev environment using the latest release of the kit.
My expectation is that the maker add function on the coe-cli should add the ALMAcceleratorServicePrincipal and permissions to the maker dev environment, is that expectation correct ?
As it doesn't, not did it give any error. Manually adding the S2S user and assigning it Sys admin role solves the issue and PAC CLI can connect and publish (and presumably export in this issues instance)
Hi @mikefactorial and @devkeydet,
I am facing the same issue, the application user was not created on the target environment. Could you please also set checkbox "Grant access permission to all pipelines" within the newly created Service Connection when using commands "coe alm maker add" and "coe alm install"?
Thank you!
@dylanhaskins and @Reinhard-S thanks for the feedback will investigate this and see what we can do to clean it up.
Closing this out as this will be handled in the Admin app in an upcoming release. We are de-investing in the CLI in favor or the admin app for setup and maintenance in the ALM Accelerator going forward.
@jenschristianschroder who is working on the ALM Accelerator Admin app features for visibility.
Describe the issue
Expected Behavior
No response
What component are you experiencing the issue with?
ALM Accelerator Pipelines
What solution version are you using?
August 2022
Steps To Reproduce
No response
Anything else?
No response
AB#1209