Create a fork?

[F21]

It's been quite a while since @Lucretius was active on GitHub and the last commit to this repository was back in October 2021.

Personally, I still find this project to be really useful and use it along with Vault quite often. What does the community think about creating a fork to maintain and improve the project?

[Lucretius]

I am no longer working with Vault, and have not been for some time so I will no longer be maintaining this project. @F21 if you or others wish to make a fork of this project and continue maintaining it, please feel free to do so. I am glad you are able to get use out of it.

[F21]

Thanks @Lucretius !

One small thing, can you add a license to the project so that forks can inherit or use a compatible license? This would be legal clarity for future contributors and users.

I started a fork here: https://github.com/Boostport/vault_raft_snapshot_agent

[Lucretius]

I've added an MIT License to the project - feel free to continue developing on the fork!

[F21]

Thanks so much @Lucretius !

[Argelbargel]

Hi, first off: thank you @Lucretius for a great tool
I too started a fork. You can find it here: https://github.com/Argelbargel/vault_raft_snapshot_agent

It started with some simple changes and some github actions to publish container images and a related helm chart (which can be found at https://github.com/Argelbargel/vault_raft_snapshot_agent-helm).

Then i thought, we not try to really understand this go thing (i'm a java developer by profession) and started to incorporate improvments from some other forks (mainly @F21's great ideas) and the open pull-requests for this project and some of the feature-requests still open here.

Take a look and please provide feedback. As I only use vault-raft-snapshot-agent for storing snapshots locally, i'd be happy if someone could help test the other storage options ;-)