Is your feature request related to a problem? Please describe.
Deployed Parse server using k8 and used /parse/health for the readinessProbe and livenessProbe probe. But when deploy new code and broke the database connection, /parse/health still returns 200 OK. So old container was killed and new broken one brought online

Describe the solution you'd like
Only return 200 ok after db is

Best I can tell, all executables produce 0 as a Linux exit code, regardless how wrongly they were invoked. That's a problem, e.g. when attempting to run the gateway as a systemd.service.

Specific use case: storj-gateway.service runs gateway_xxx_yyy --config-dir does-not-exist. Systemd happily reports that everything is fine -- which of course it is not, but it cannot tell unless the exit co

As a first effect of #1287, we should react to the reporting of I/O errors with a notification that the service is down. This concerns the rawx, meta0, meta2, meta2 and sqlx service types.

• manage in sqliterepo (meta*, sqlx)
• manage in rawx

infinit user pull       
Remotely deleted identity for user "bushbaby123".

not sure if it actually deleted the user, but this does not sound correct

v0.8.0

This is a feature request.

Access-Control-Allow-Origin, Access-Control-Allow-Methods, Access-Control-Allow-Headers and Access-Control-Allow-Credentials header is required to satisfy https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Origin.

When we have more than one ExternalDNS, they appear in the same line which is confusing
We should print each address in its own line.

Could you please include some notes how to configure this extension?
The blind installation shows a "white screen of death" at the S3 tab.
Thanks!