Abandoned Project?

[RaymondArias]

I am wondering if this project's maintainers are actively developing this project, last commit was a few months ago and there are issues that need to be resolved.

If they are not then someone should fork this project and continue development.

@szibis or @mhyllander if either could let us know whether you guys are still working in this project that would be helpful

[mhyllander]

Hi, I agree that there is little progress in this project, which is too bad because it's a very useful plugin. I'm not a maintainer, I've only contributed one PR. For the moment it's fulfilling my needs, but I see that there are several PRs waiting with bug fixes and improvements.

[mhyllander]

After my PR was merged, @szibis said he was going to do some changes before releasing version 2.0.0. I think he is working on that in #70.

[farrellit]

I think if it takes months to make changes, this project either needs additional maintainers or the community needs to fork it.

[skang0601]

@szibis Are you interested in additional maintainers or passing on this project? I see several PRs hanging that I'd like to get merged in honestly.

[farrellit]

If they are not then someone should fork this project and continue development.

I'm sure @szibis is at least as busy as the rest of us. This repo is featured in the helm upstream, and it has lots of value. It has to be able to grow along with the fast moving helm ecosystem.

I'd like to see if folks here have interest in a community operated organization to own this project. That way it's not tied to anyone's personal participation. I don't see any testing of this, so maybe that's something we could improve for quicker PR acceptance. If we end up somewhere happy, we can petition helm docs to update to our fork. I think it's important that we demonstrate at least the quality of the existing repo.

I've already created the org and am sending invites to all contributors, but this discussion is very much still open.

[sstarcher]

@szibis Could you possibly add some additional maintainers to this repo so we can keep it alive without needing to fork it?

[szibis]

I am back. Open to talk and we will have more people to work on this project and plans. I was out-of-focus but now we need to move project forward with full focus.

[szibis]

@sstarcher Yes I am open to new maintainers and we will have time for this project in our team.

[sstarcher]

@szibis great to hear. I'm wondering what your overall goal is for helm secrets. Would you be interested in adding additional provider support like vault or is the goal to keep this simple and focused on sops.

[Just-Insane]

Support for a secrets backend like Hashicorp Vault would be greatly appreciated.

It would also be nice to see examples of using helm-secrets with Helm's stable charts in the documentation.

[szibis]

Yes. Hashicorp Vault is something we like to consider in the project.

First, we need to clean issues and merge PR's with a defined roadmap.

Add more maintainers and focus on the current state of helm-secrets with 2.0 release that needs to be added to all projects that use helm-secrets like helmfile.

[Just-Insane]

Yes. Hashicorp Vault is something we like to consider in the project.

First, we need to clean issues and merge PR's with a defined roadmap.

Add more maintainers and focus on the current state of helm-secrets with 2.0 release that needs to be added to all projects that use helm-secrets like helmfile.

Do you have any thoughts on how we want to impliment Vault support? Looks like there is an open issue on SOPS to add Vault as an alternate KMS service (getsops/sops#291).

Alternativly, we could use Vault as a KV store, which would be similar to how Ansible's Hashi_Vault works.

I think the prefered option would be the second option, to have it pull values from the KV Store, as adding it as another KMS resource does not give us flexability in storing data.

[jkroepke]

I did it (create a own fork): https://github.com/jkroepke/helm-secrets/

If you still interest in vault support let me know here: https://github.com/jkroepke/helm-secrets/

[sstarcher]

@jkroepke creating a fork does not seem to be a great idea. This project is still being maintained and it would be helpful if you would help them maintain it vs forking the project as @szibis is open to additional maintainers.

[jkroepke]

still being maintained

It doesn't feel like this.

[sstarcher]

Last commit 7 days ago. Have you reached out to @szibis asking to be a maintainer?

[jkroepke]

@sstarcher

As I understand @szibis isn't a member of this repo anymore. His status on the Comment left is "Contributor" not "Member" or "Owner".

@zendesk has the maintenance now.

Edit: It looks like @szibis is also a member of @zendesk but the current status of the project is still unknown for me.

Last commit 7 days ago.

Just update the licence without touching any PR or issues after 2 years.

[sstarcher]

Great, now let's give them some time to respond before we start abandoning ship.

[jkroepke]

@sstarcher 3 weeks ago. Until now, just an other copyright update.

How long we want to wait?

[sstarcher]

Looks like they are not responding. @szibis are you going to add collaborators for this or should we consider it a dead project?

[jkroepke]

For me it's for a dead project now.

I will start to maintain helm-secrets @ https://github.com/jkroepke/helm-secrets now.