kube VS git-cliff

https://github.com/kube-rs/kube/blob/main/kube-client/src/api/portforward.rs ill create an issue and start working on implementing it. Thanks for the feedback

Interesting, I haven't tested that one yet. We use kube-rs (https://github.com/kube-rs/kube) under the hood, which does automatically token refresh when needed. But there might be some edge cases not considered.

So I used kube-rs and came up with this: https://github.com/mach-kernel/databricks-kube-operator

Stackable is building k8s operators in Rust for bringing up interconnectable, data crunching applications (being able to bring up a complete data platform on any k8s cluster is the goal). kube-rs is used under the hood and code is open source.

yes, we had a very small API to create who created role bindings for a CI. I chose Rust because it was easy and seems easily maintainable with the kube-rs https://github.com/kube-rs/kube-rs crate

I have experiencie on this. I'm a DevOps engineer that started before DevOps was a thing, and I want to write rust for a living. What I'm doing is writting rust for tooling and kubernetes controllers using https://github.com/kube-rs/kube-rs. Rust and DevOps are close specially if you need to write your own tools. My recommendation is if you have some space to solve problems at your job with rust go and do it, if not try some opensource projects that interest you to get more experience.

git-cliff is a terminal tool that can generate changelog from the Git history by using conventional commits, as well as by using regex-powered parsers and you can even change the changelog template itself by using a configuration file. This tool is a great example of text parsing on the terminal and also uses clap_mangen which generates man pages. Useful for anyone who is serious about looking into making a production-ready terminal tool!

Solutions exist for this. Our company does this with git-cliff. Using conventional commits, any commit labeled with the subject "www" will appear in our public changelog.

This was primarily aimed to work with git-cliff to generate changelogs for GitHub releases, since tagging contributors would include them as contributors for the release, while also ensuring structured changelogs thanks to git-cliff. As of now, it requires a few extra steps to get it working with git-cliff, but the integration should be much better once the PR for post-processors is merged.

It's the first time I see someone combining gitmoji with conventional commits (I use the later now for all my project, to generate my changelogs automatically with with git-cliff.)