cfssl icon indicating copy to clipboard operation
cfssl copied to clipboard

Published 20 hours ago • verified publisher icon cloudflare

Goose database migration tool

Open CtrlC-Root opened this issue 8 years ago • 4 comments

I was just wondering if you are still using the https://bitbucket.org/liamstask/goose version of Goose in production? It seems that project is dead and as far as I can tell there's no clear successor among the existing forks. If you are still using it would you consider adding it to the vendored libraries?

CtrlC-Root avatar Jan 23 '17 04:01 CtrlC-Root

Looking at goose "successors" lately, I've found that https://github.com/pressly/goose seems the most maintained. But as far as I can tell, it feels like it's still a one man based effort.

gautaz avatar Oct 26 '17 05:10 gautaz

So I was only using Goose so I could run CouldFlare's cfssl tool (https://github.com/cloudflare/cfssl). I recently discovered that Hasicorp's Vault (https://www.vaultproject.io/) can do everything cfssl can do using a few plugins and I intend to switch to it. I wanted to post that here in case that's why others are building and using Goose. If you're using it for something else obviously this won't help.

EDIT: Whoops, didn't realize this was on the cfssl repository. Well, most of my comment still applies.

CtrlC-Root avatar Oct 26 '17 18:10 CtrlC-Root

@CtrlC-Root Strangely, I was also considering the shift to vault. The only thing that is missing is the OCSP responder but the Vault Team considers it a bad practice.

I have asked for a more detailed explanation on this particular point yesterday: https://github.com/hashicorp/vault/issues/2631#issuecomment-339567892

gautaz avatar Oct 27 '17 08:10 gautaz

Should we just use https://github.com/pressly/goose? It looks popular and maintained. I tried it with PostgreSQL the other day and it worked fine. I can open a PR to update documentation/instructions.

hag0p avatar Mar 06 '25 19:03 hag0p