So, to clarify, the reason this is a TODO is because we need to carefully test all the workflows we reasonably can and make sure at least all the code in this script doesn't break. 😅

(Just adding -u is the easy bit 🙈 ❤️)

I figured it might be a bit easier said than done since it wasn't already completed but wanted to submit it just in case it was missed in this particular file. How do you want me to proceed to help?

Sorry -- I think the first step would be to enumerate all the things we want/need to test. The best place to start with that (IMO) is looking through the script for all the "configurable bits" (environment variables we actually act upon) so we can create a plan for verifying that they all still work appropriately.

Essentially anywhere we call file_env or have an if with a variable, we should figure out a plan for testing that the relevant code still works with -u enabled. 👍

If we do add -u, that would be likely breaking for more users than we expect for their initdb.d scripts: