adobe / adobe/aio-cli-plugin-cloudmanager
pipeline:create-execution: Write execution id to stdout
- Langage dominant
- JavaScript
- Étoiles
- 50
- Forks
- 36
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
It is useful to have the id of the newly created execution id available in the stdout (for non-interactive use cases).
This is not the case for https://github.com/adobe/aio-cli-plugin-cloudmanager/blob/b95ae82604c89f2bf8512c36cb7d5ca023dc1864/src/commands/cloudmanager/pipeline/create-execution.js#L35 as the spinner is overwriting output in stdout.
The only way to get hold of the output is via the {{-a}} option: https://github.com/wblachowski/cm-jenkins-helpers/blob/7762702130cec073abddef51eb4268a8d28465bd/jenkins-config/pipelines/pipeline-cm-deploy.Jenkinsfile#L14
The return value of of the run method is not evaluated. A table should be emitted similar to what is done in https://github.com/adobe/aio-cli-plugin-cloudmanager/blob/b95ae82604c89f2bf8512c36cb7d5ca023dc1864/src/commands/cloudmanager/execution/get-step-details.js#L42. That way both json and regular format could be supported.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start in src/commands/cloudmanager/pipeline/create-execution.js at the execution creation flow and compare its output handling with src/commands/cloudmanager/execution/get-step-details.js. Check how the run method's return value is currently handled; done means the new execution id is available on stdout without spinner interference, with both regular and JSON output supported.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- javascript
- Domaine
- cli
- Type d'issue
- Fonctionnalité
- Difficulté
- 2/5
- Temps estimé
- 1-3 heures
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 50/100