Repository navigation
feat(ci): add catalog pipeline templates and automated updates - #678
Brilly-Bohyun wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
lets create a custom repository for this, any good name ideas?
There was a problem hiding this comment.
How about "Kubara-action"?
| func CreateCatalog(catalogName string) error { | ||
| return createCatalog(catalogName, false, false) | ||
| } |
There was a problem hiding this comment.
wouldn't this become deadcode now? there isn't any other reference to it.
There was a problem hiding this comment.
Totally my mistake, I'll delete right away 🙇🏻♀️💦
There was a problem hiding this comment.
wouldn't it be better to have those two as options for kubara init like the renovate file we automatically add?
There was a problem hiding this comment.
That makes sense. I'll add both as options to kubara init, following the Renovate setup.
6543cb2 to
dbb11b1
Compare
dbb11b1 to
fb13683
Compare
|
@tuunit Removed the unused |
|
Looks like we had a similar idea around the same time 😄 I opened #676 to run Yours covers more ground with GitLab support and the reusable action. Might be worth aligning the two approaches! |
This branch has not been deployed
3 participants
Summary
Add GitHub Actions and GitLab CI examples that update the official bootstrap and general catalog versions, run
kubara generate, and open or update a PR/MR when configuration or generated artifacts change.--github-actionsand--gitlab-cioptions tokubara catalog createfor catalog validation pipelines.Closes #573.
Change type
Breaking change
How I tested it
kubara initandkubara generate, followed by Helm and Terraform validation in CI.Notes for reviewers