Feature Request: Notification of failed startup script

[glasnt]

#46 (comment)

I realize it's a bit out of scope for the PR, but looking at this startup script, it took me a double-take to realize we probably don't want to run with set -e because we want all these things to happen, they don't depend on each other. It might be worth adding a comment to explain.

#46 (comment)

How do we know if something goes wrong with the startup. For example, what if the migration job stops working? Does something alert, or is this a place we should consider adding a log-based alert?

[glasnt]

#46 (comment)

Since metadata startup script runs async to TF, it can't block TF, so we'd need to have a separate process for that.

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days

[glasnt]

We no longer use startup scripts, closing.