This tweaks a couple things I ran into running STN in GKE:
Allow for not setting the project ID (will default to the GKE cluster's project, which is what we want)
Warn if credentials are unset (there are a couple ways you can do this, and the failure modes are rather inscrutable to debug otherwise)
Send logs to stdout. In GKE, you just do the standard k8s thing of printing logs to stdout/stderr. However, logs on stderr are considered "errors" regardless of the application-level severity in the JSON payload. It looks like:
I investigated the checks framework at @harrislapiroff's suggestion but since it normally doesn't run in production and seems more suited for static checks I thought it would be better to just use logging directly and not add a run of the check tool to how we start the app in prod.
This tweaks a couple things I ran into running STN in GKE:
I investigated the checks framework at @harrislapiroff's suggestion but since it normally doesn't run in
productionand seems more suited for static checks I thought it would be better to just useloggingdirectly and not add a run of thechecktool to how we start the app in prod.