Florian Hines

:shipit: and live on hub via https://github.com/meltano/hub/pull/907 !

Related - https://github.com/meltano/meltano/pull/6742#issuecomment-1249513809 ...also floated some state related integration tests there.

> Would https://github.com/meltano/files-airflow/issues/32 solve it? @tayloramurphy I might be misunderstanding but I think @pnadolny13 has a need for more "dynamic" env vars. Things you define in the schedule config would...

> I'm approving this PR because for development, setting FLASK_DEBUG=True makes sense, but there may be a larger issue here. 👍 I think that makes sense, and also agree that...

>Could someone try to verify following these steps @dingobar at some point I stuck`FLASK_ENV=development` in my `.zshrc` and promptly forgot about it - so initially had some issues reproducing this...

> FLASK_DEBUG=True not working seems to be a bug? I'm not certain, actually. I don't know if FLASK_DEBUG=True should mean that cors restrictions/host checks are loosened automatically, feels like that...

> Also the steps confuse me - are you serving the UI with meltano ui or yarn serve? Or some mix thereof? @WillDaSilva its both > As far as I...

fwiw - We already produce logs for all `elt` & `run` invocations that aren't controllable by users. Related: - https://github.com/meltano/meltano/issues/3111

@ReubenFrankel @aaronsteers I'm actually ok with the second option/format. In that case I think we could just use ":" as another deliminator and basically use that as our "official" segment...

> @aaronsteers since we have MELTANO_PROJECT_ROOT I like keeping "root" in the name. My preference would either be MELTANO_TEMP_DIR_ROOT or MELTANO_SYS_DIR_ROOT I'm a no-go on `MELTANO_TEMP_DIR_ROOT` because I think that...