Matthew Fisher
Matthew Fisher
See https://github.com/deis/charts/pull/142
If we were to stop the container in the middle of a base backup, it is unknown what will happen to the backup. See https://github.com/deis/postgres/pull/104#discussion_r65463009 for discussion/potential solutions to this...
Right now if you attempt to add the following envvars and disable routing, the application won't deploy because it relies on the hard-coded secret paths: ``` > deis create postgres...
Optimally we should be able to test on all four supported backends (minio, aws, gcs and azure) so we can ensure that it all works across all supported backends.
Right now all different storage backends are configured in one giant python script. This should really be broken down into separate scripts (`/bin/create-$DATABASE_STORAGE-bucket`) so it's less of a maintenance hassle.
This way we can start a job which will create self-installing packages, much like what we did for the deis v1 client and deisctl release process. Alternatively, if we can...
We need to ensure that the in-place upgrade path is fully tested by Jenkins for a release. continuation of https://github.com/deis/deis/issues/4517
cross-post of https://github.com/deis/deis/issues/4037 > @jchauncey has found some interesting problems when running significant load through deis. I'd like to see an automated version of this test (or similar) so that...
See https://travis-ci.org/deis/logger#L197-L198