You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once above is set you can start the pipeline, but it's gonna fail immediately at validation stage with the following message:
Failed: Invalid pipeline: . Reason=Branch=this-branch-does-not-exist not found in repository (Finished: September 22, 2021 11:14:23 AM GMT+2)
In contrast repository ID is being validated, so I assume that it may require some backend API changes:
$ aio cloudmanager:pipeline:update PIPELINEID -p PROGRAMID --repositoryId=123456
updating pipeline... failed
› Error: [CloudManagerSDK:ERROR_UPDATE_PIPELINE] Cannot update pipeline: https://cloudmanager.adobe.io/api/program/PROGRAMID/pipeline/PIPELINEID (400 Bad Request) - Validation
› Error(s): Referenced repository not found in application or is not ready for use: 123456
› Code: ERROR_UPDATE_PIPELINE
The text was updated successfully, but these errors were encountered:
It could certainly make sense for this CLI command to accept a flag --validate-branch which gets the repositoryId (either from the current pipeline definition or the repositoryId flag), lists the branches, and validates that the branch is one of those. That wouldn't be possible for tags, however.
Expected Behavior
User input (branch/tag/repositoryId) must be validated upon update of CM pipeline settings.
Actual Behavior
aio cloudmanager:pipeline:update
ends successfully for not existing branches/tags.Reproduction Scenario, Platform, and Version
Steps to Reproduce
Once above is set you can start the pipeline, but it's gonna fail immediately at validation stage with the following message:
In contrast repository ID is being validated, so I assume that it may require some backend API changes:
The text was updated successfully, but these errors were encountered: