softwaremill / softwaremill/bootzooka
Deployment previews
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 786
- Forks
- 149
- Avg merge
- 2h 22m
- Merged PRs (30d)
- 112
Description
What would it take to create "development previews" for PRs coming into a bootzooka-based project?
We already have a helm chart for k8s deployments, and we deploy a sample bootzooka installation to k8s. Could we create internally and document externally a flow in which PRs (probably not all, but somehow "approved" or "trusted"), after a successful build, are deployed to k8s as well? The PR should get a comment with a link to the deployed instance. After merging or a PR update, things should be cleaned up.
As an inspriation - see how this works using e.g. netlify
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the existing Helm chart and the sample Bootzooka installation deployed to Kubernetes. Compare the requested pull-request preview flow with the Netlify approach, including successful builds, trusted or approved PRs, comments containing deployment links, and cleanup after updates or merges. Done means the flow is implemented and documented externally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100