This commit makes it able to overwrite `--tls-verify` on push. It moves to the end of the command the variable `PARAM_PUSH_EXTRA_ARGS`. Otherwise you will have to disable `TLSVERIFY` for pull actions too and that is not desirable. This way one can run the action with the parameter `PUSH_EXTRA_ARGS=--tls-verify=false` and being able to push to an insecure registry. But still maintaining the TLS checks on build.
Add a new version of the catalog publish step action. This
new version API is backwards compatible, as it adds one new
optional parameter only, `TKN_ARGS`.
The new version includes the following changes:
- latest version of tkn image set by default
- sets two OCI labels org.opencontainers.image.description
and org.opencontainers.image.version for each resource
- accepts TKN_ARGS which is passed to all resources and
can be used to set additional OCI labels as well as other
settings
Signed-off-by: Andrea Frittoli <andrea.frittoli@gmail.com>
Update jira-get-ticket-status.yaml
Add SHA instead of tag named
Changed secret name and now have a parameter to specify the value
Improve documentation
Improve documentation
Update api version and minimal pipeline compatible version
Fix trailing spaces on python code
As we are also publishing `StepAction`s (and maybe one day `Pipeline`s
?), the path to where the tekton bundle are pushed for `Task`s
changed.
Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
This task is designed to be used as part of an implementation of the GitOps Rendered Manifests Pattern.
It is intended to be unopinionated and as such will simply template a Helm chart and output a file to a workspace volume with an optionally specified name and location.
* first submission
* changed to non npm source repo
* added params to the hugo task
* added readme
* removed platform restriction doc
* updated task and readme
* added task description
* used fully qualified registry name for docker image
* updated OWNERS
* tagged image with digest
* updated `apiVersion` to `v1` from `v1beta1`
This PR deprecates the old and broken Tasks because
they are now throwing errors. They are old and not
actively maintained which is why we decided to deprecate them.
