-
Story
-
Resolution: Done
-
Major
-
None
-
None
-
5
-
False
-
None
-
False
-
-
-
AppSvc Sprint 237, AppSvc Sprint 238, AppSvc Sprint 239, AppSvc Sprint 240, AppSvc Sprint 241
Owner: Architect:
David Peraza
Story (Required)
As a Primaza developer, I will like to be able to release primaza, so that it can be consume by customers via primazactl
Background (Required)
We need to be able to create a release of primaza including the control plane image, agent images and manifest bundles for both control plane and agents.
Glossary
NA
Out of scope
Helm, Operator Hub, Artifact Hub, downstream release
In Scope
Github Artifacts upstream
Approach(Required)
Create a workflow that is run when a git tag (semver) is pushed on main branch trigger.
The workflow will build images, push to GitHub Packages (ghcr.io/primaza/primaza) with the version tag and create the manifest bundle pointing to those images. Manifest bundle will be delivered via GitHub artifacts upstream.
Demo requirements(Required)
A good demo will create a semver tag on a commit on main. The push of the tag will result in the release build, packaging and delivery via github artifacts.
Dependencies
NA
Edge Case
NA
Acceptance Criteria
Release (draft) github workflow is in place
First release v0.1.0 is done
Documentation in place explaining how to make a new release
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
v
Legend
Unknown
Verified
Unsatisfied
- blocks
-
APPSVC-1348 Allow primazactl to reference a specific version when installing primaza
- Closed