Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains a "release pipeline" which is designed to take care of the release process for us, the idea being that we on-board the securesign/releases repository and control the release via pull requests, i.e we could run staging pipelines on pull requests to the securesign/releases repository and when merged we could run the actual release. The pipelines can be controlled by configuring the params passed in through the on-pull, and on-push tekton files like shown below.
Params
The pipeline itself works by first applying all the files passed in through the releasePlanDir param, then moves on to apply files in the releaseDir, then continues to monitor the progress of the release until it passes or fails.
In order to generate staging resources for each release CR the label
needs to be applied to each releasePlan, this allows the pipeline to replace the actual prod RPA with the staging one