kubernetes-management VS meta-package-manager

Kind of, the reason why it's a bit difficult to describe the project is because the different component mean different things to different people.

I built updatecli so I could use it to help me maintain infrastructure as code, then bit by bit, I discovered how other people were using it to solve challenges that I didn't imagine.

Scenario 1: https://github.com/jenkins-infra/kubernetes-management/blob/...

We monitor the latest Certmanager chart version available and we bump our git repository so Helmfile can pick the latest version and update our Kubernetes clusters.

If you are looking for real k8s production experience, you could participate to an open infrastructure project. the Jenkins infrastructure is one of them which mean we try to be as open as open possible in meeting, in doc,and almost every git repository are public. You can start review pull request from https://github.com/jenkins-infra/charts and we automate many many more :) otherwise you could also participate in other open infrastructure project such as the Wikipedia one. Disclaimer: I am the lead infra of the Jenkins infrastructure project so feel free to dm me if you want more information.

For Helm, they are different ways to automate helm chart releases depending on the tooling you have access to. On the Jenkins project, we use a command-line tool named updatecli that I build to help us automate file content like for Docker, Puppet, Helm, Yaml and then run it from a Jenkinsfile, it doesn't update Changelog yet.

Something like Meta Package Manager? https://github.com/kdeldycke/meta-package-manager

I use https://github.com/kdeldycke/meta-package-manager

The result: https://github.com/kdeldycke/meta-package-manager/commit/3ab...

Source: https://github.com/kdeldycke/meta-package-manager/

With regular snapshots you can at least eliminate new installed software as the root cause of an issue. Doesn't solve the issue with preferences though.

and let it figure out which package manager to use to install your package.

The project is open-source: https://github.com/kdeldycke/meta-package-manager#readme

This CLI has some other capabilities, like listing the duplicate packages on your system:

    $ mpm list --duplicates

Potentially somewhat answering my own question (but not completely; i am still interested in your answer) you might be interested in https://github.com/kdeldycke/meta-package-manager is it along the same lines?