steeling
steeling
Ya it's true that through clever tricks and staged migrations between application and schema updates you can create roll forward and back scenarios. However that burden can become greater than...
To provide one other important piece of info, we're looking to do this with helm, and helm hooks. Helm stores previous chart state, so we can't easily release a compacted...
A better example might be simply dropping a non-null column in a db that a previous code version requires The issue we have, while using helm, is that a rollback...
To my last question, I guess it's actually possible to provide both options. I was thinking of the scenario of running a Migrate() on a Dir, and tying a max...
Unfortunately all the configs are controlled by helm, which will overwrite configs on releases and rollbacks. We could append a unique ID to each one, but then we're left with...
+1 on switching to stdlib, i use a framework that check errors with errors.Is and translates to a corresponding API error. Incompatible with the current approach, need to add some...
> @teejays you should checkout https://godoc.org/github.com/lib/pq#Array which will handle properly formatting using the postgres array format. @doug-martin this this doesn't work when trying to insert structs via `goqu.Insert("posts").Rows(myPosts)`, unless the...
we also need to add the Vault Port to the VaultSpec
> Hmm good question! I was actually surprised to see that we don't use certKeyBitSize for the CA generation for tresor. If we switch that, then that means a certKeyBitSize...