400 message: Validation failed assets link
Summary
I get the below error when I pass using the release-cli "assets": { "links": { "name": "Project Container register", "url": "https://gitlab.test.com/project/container_registry/" } }
which is just a link and not passing a file. I am able to do this manually in the release ui.
Steps to reproduce
"name": "Project Container register" "url": "https://gitlab.test.com/project/container_registry/"
release-cli create --name $RELEASE_TAG --description "$RELEASE_NOTES"
--tag-name $RELEASE_TAG --ref $CI_COMMIT_SHA
--released-at $CI_COMMIT_TIMESTAMP
--assets-link '{"name": "$CI_PROJECT_TITLE Container Registry", "url":"$CONTAINER_REPO" }'
What is the current bug behavior?
Validation Fails. Does not seem like a release-cli problem, but I am not sure.
What is the expected correct behavior?
url added to the release
Relevant logs and/or screenshots
time="2021-02-17T13:56:49Z" level=fatal msg="failed to create release: API Error Response status_code: 400 message: Validation failed: Links url is blocked: Only allowed schemes are http, https, ftp" cli=release-cli version=0.6.0
Edited by Jaime Martinez