Is this project dead?

[jeffgus]

Little to no activity. No mention of a release for Openshift 4.10, 4.11, or 4.12.

What alternatives are there? Is argocd-autopilot a good fit? I installed ArgoCD on OpenShift using the operator and have yet to try autopilot with this configuration.

[wtam2018]

@jeffgus This project is not dead yet. kam CLI continues to be shipped with OpenShift GitOps.

[jeffgus]

I see the version matrix has been updated. No movement on pull requests.

[wtam2018]

We've been busy. :-)

[harrietgrace]

Hey @jeffgus! How have you been using kam? As a bootstrapping tool to get your environment started for new projects? A way to get a test env up? Something else? It would help us with planning for the future of kam to know how folks are using it 😊 Also, are there particular PRs that you're waiting on? Any features missing that you're keen to see added?

[jeffgus]

Hey @jeffgus! How have you been using kam? As a bootstrapping tool to get your environment started for new projects? A way to get a test env up? Something else? It would help us with planning for the future of kam to know how folks are using it blush Also, are there particular PRs that you're waiting on? Any features missing that you're keen to see added?

I used it to bootstrap my ArgoCD config. I also added additional environments and apps into the config. It simplified setting up a gitops env. I'm still a little unclear where to draw the line on kam and tkn-pac. I'm using pac for the application build. Anything that is simply customizing an image (just a Dockerfile), I keep in kam.

Currently, kam refers to a ClusterTask (buildah). I've read that a ClusterTask is deprecated and will be replaced by cluster resolvers. Is there a plan to update kam to support this?

I also submitted a change ( PR #325 ) that updates the use dryrun command with the newer parameters. It is not clear to me why the tests didn't pass. I never received a response as to what I would need to do to fix the test failure.

Also, no response to #320.

Lack of response makes me think the project is being neglected.

[jeffgus]

crickets

[zokusai]

Hey @jeffgus! How have you been using kam? As a bootstrapping tool to get your environment started for new projects? A way to get a test env up? Something else? It would help us with planning for the future of kam to know how folks are using it 😊 Also, are there particular PRs that you're waiting on? Any features missing that you're keen to see added?

Hi Harriet,

To contribute to your question, I am currently evaluating the use of the tool to facilitate management by the project teams of our clients and I would like to know the roadmap that you have planned.

So far, I've used it for bootstrapping and demos, with some limitations due to the client environment. Specifically, I had to recompile the tool to:

• Work with a legacy version of the gitlab API (8.0/v3).
• Disable SSL verification in communications and in the configuration of the webhooks created.

Unfortunately, it was done in fast mode, not worthy of a PR, but I still wonder if the tool will be more flexible and configurable in the future, so as not to burden projects with the maintenance and updating of an external tool, which would make it difficult its adoption greatly.