Missing 'pre' lifecycle hook

[cvarjao]

When the database pod is not yet available the mid lifecycle hook fails. We can avoid that by adding a pre lifecycle hook that will wait (Retry) until the database pod is up.
something along the lines of the existing Init Containers which protects the pod form startup if the database is not available, but it doesn't protect against the deployment.

Reference

• Lifecycle Hooks

[cvarjao]

Fixed on PR #714

[garywong-bc]

We should talk.. the mid-lifecycle hook ONLY serves to call post-deploy.sh which acts upon the (single) database. If we can put it in the Jenkins pipeline, for DEV/TEST and PROD then we no longer need this. We'll also separate out the DB_REPLICATE logic as this is no longer needed on DEV (fresh dataload everytime), nor on TEST (no overwriting of whatever is there), nor on PROD (replication will planned and co-ordinated).

I'm ready to do this anytime as it'll negate the need for a this task. @cvarjao @DerekRoberts

[DerekRoberts]

@garywong-bc Good idea! I'd be happy to help.

@cvarjao Any opinions?