These pipelines are in standard tekton format. They can be found in ./pac/pipelines and ./pac/tasks.
Depending on the use case there are two ways of consuming of the RHTAP pipeline:
For this scenario, the RHTAP pipeline definition can be directly referenced from the official repository. In such case, all the updates and security pathes will be available immediately. No actions required from the consumer side.
If any customization to the default RHTAP pipeline definition is needed or immediate updates are not desired, workflow described in this section should be taken.
Fork this repository and modify the default RHTAP pipeline definition according to your needs. Reference the modified version of the pipeline.
To consume CVEs fixes and pipeline updates, one should rebase changes in the fork on top of the new RHTAP pipeline version.
Modify the template placeholders to match your backstage template vars
Note, PaC also has {{variables}} and you should not modify those.
{{values.appName}} -> ${{ values.appName }}{{values.dockerfileLocation}}-> ${{ values.dockerfileLocation }}{{values.namespace}}-> ${{ values.namespace }}{{values.image}}-> ${{ values.image }}{{values.namespace}}-> ${{ values.namespace }}{{values.buildContext}}-> ${{ values.buildContext }}{{values.repoURL}}-> ${{values.repoURL}}