New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Resolve PaC params as default #1397
Comments
yeah, we don't resolve params on remote resources.. I am not against adding it.. (as well having remote tasks from remote pipeline annotations). any chance you can fill in a RFE on red hat access so we can prioritize this? |
Hi @chmouel, I'll be happy to pick that up. Could you explain what an RFE entails, and how the process works of filling one in on Red Hat Access works? |
@chmouel I created an RFE: https://access.redhat.com/support/cases/#/case/03620521 |
We have added some of the default Pipelines-as-code parameters to the parameter list of the PipelineRun like this:
Adding these values as a default in the Pipeline spec and omitting it in the PipelineRun doesn't seem to resolve the params.
Pipeline.yaml:
PipelineRun.yaml:
For example when using a github-set-status task I get the following error:
http.client.InvalidURL: URL can't contain control characters. '/repos/< organisation>/{{ repo_name }}/statuses/< sha>' (found at least ' ')
Would it be possible to enable using pipelines-as-code parameters as default values in the pipeline spec?
The text was updated successfully, but these errors were encountered: