[Feature] Publish Extension Installed Apps

[panas78]

There are cases that during a Batch Publish and Install step using the ALOps Extension API
, although the process finishes with no errors , the app is not actually installed but remains just published.

That causes a false sense of everything is ok but actually that is not the case. What we do now is to either login to the enviroment and check everything is properly installed or rerun the pipeline and check the installed apps at the begining.
A list with the actual installed apps (from those sent) in the end of the process will be an idea to verify the correct completion of the process.

[waldo1001]

Well, that can happen - but only if people to manual things in the environment.

We're trying to be smarter here with the extension api. It's different API's we need - you can't do this with the updateExtension API, you need extra API calls for this.. so .. we need to deviate from default BC behavior. But we can do it - just need some time.

[panas78]

For now , i created an extra step at the end. Get the extensions from the API and compare them with the apps from $(System.ArtifactsDirectory) . But for sure it would be nice to have something like that inside the Alops step.

[thomari]

#943 (comment)

I described the same issue here. An App can also be published but not installed, if the schema sync fails.
Skipping those apps leads to confusion and more manual work.

Maybe a solution would be a toggle like "Skip uninstalled Apps"?