Closed PeterConijn closed 1 year ago
Hi,
If you publish with VSCode, it's going to be published in a different scope as if you would publish with the API or with the page in BC.
Since it seems you try to install an app in the APpSource number range, a dev-port deploy is the only thing you can do. For that, we have the "dev endpoint" setting. You are using the "api endpoint", which will trigger a normal deploy - which will never work with your numberrange.
So - empty the api_endpoint. And fill the dev_endpoing with "https://api.businesscentral.dynamics.com/v2.0/YourEnvironmentName/"
Please let me know if that works or not!
Hi!
Thanks for the tip! You can't clear the API Endpoint, since that is a required field in ALOps, but ALOps is clever enough to overrule it with the Dev Endpoint when that last one is filled.
That will solve our immediate issues, but it brings the question to mind how one would install a PTE on a customer's Production using the ISV licensed object ID range(s); but that is a question for future Peter.
You can't 🤷♂️. The only way to install an ISV License object to production, is AppSource (afaik).
Describe the bug After not being able to resolve the issues on #592 we decided to push for cloud environments. We have now two Acceptance environments on 21.2 and have been able to publish our apps from VSCode (Dev) into both databases.
Next step was to repoint DevOps releases to the new environments. We have had some hurdles (authentication, url configuration), but now we are running into an error we cannot quite figure out.
We are using the ALOpsExtensionAPI module, which results in the following error:
Being good little debuggers, we checked the extension deployment status and it revealed the following issue:
This seems to be because ALOpsExtensionAPI is publishing it as a PTE, but should it not take the ISV app ranges as defined in the app.json into account?
the used yaml please provide the yaml that you used. It helps you put the yaml like this:
the output Also the complete output is necessary for us to see what is going on. Also use backtics:
Expected behavior I had expected (and by now desperately hoped) that the deployment would publish and install the apps.
Screenshots
Additional context I do not know if this is relevant, but the Get-BCArtifactUrl is set to use OnPrem, while we are publishing to the cloud. In the build pipelines, we use the cloud artifacts (and the build obviously succeeded)
2022-12-19T11:56:36.6592738Z ##[command]"Get-BCArtifactUrl" 2022-12-19T11:56:36.6593148Z Name Value
2022-12-19T11:56:36.6593594Z ---- -----
2022-12-19T11:56:36.6593963Z select Latest
2022-12-19T11:56:36.6594310Z type OnPrem
2022-12-19T11:56:36.6594672Z country W1
2022-12-19T11:56:36.6594927Z 2022-12-19T11:56:36.6595018Z 2022-12-19T11:56:36.6595305Z -select: Latest -type: OnPrem -country: W1