[Feature] Publish Extension Installed Apps
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 63
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named. Start by locating the ALOps Extension API implementation for the Batch Publish and Install step, then trace how completion is reported. Done means the process reports the apps that were actually installed from the submitted list, rather than only those published; run the relevant pipeline or existing checks to verify the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- api, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100