-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
AppSvc Sprint 212, AppSvc Sprint 214, AppSvc Sprint 215, AppSvc Sprint 216, AppSvc Sprint 217
Owner: Architect:
Story (Required)
As an Helm Certification Service developer I will like to be able to use chart-verifier GitHub action in our certification flow, to be able to test GitHub action as we make changed to chart verifier tool.
Background (Required)
Today we call the chart verifier through the docker image, in our GitHub workflow. Once the github action is completely integrated with our binary releases there is no need to duplicate that logic. This will simplify our flow and at the same time help us test chart verifier github action to be used in other development pipelines that output helm charts.
Glossary
NA
Out of scope
NA
In Scope
NA
Approach(Required)
By changing our flow to use github actions we will limit ourself to only make calls to chart verifier versions already released. We need to be able to run development/temporary binaries we use during testing before we create an official release. We need to enable a mechanism to be able to test in certification flow before we release. For example today we can test with container using the main tag.
Dependencies
There is a dependency with github acction already created and improved. See the action at: https://github.com/redhat-actions/chart-verifier. We will wait for github action to be running the binary instead of the container.
Edge Case
NA
Acceptance Criteria
Chart Certification flow used chart verifier github action.
Chart Verifier runs test against both binaries and containers
The is a way to test unreleased versions of chart verifier through github action
Document in chart verifier README.md the new way to run it from github actions
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied