I thought I would just put this out there for anyone else trying to run poetry with .env files for your config, the easiest way I've found is like this

env $(cat .env) poetry run pytest

Nice. I prefer that to my normal dotenv -f ... I actually don't know why I didn't start using straight env for tap development...

dotenv -f ./.env.dev run bash
dotenv -f ./.env run bash

I honestly switched to just using Meltano.

meltano invoke tap-name

works dang well for almost everything I need. (minus a debugger which I haven't needed quite yet)

Right. The situation where I use dotenv is when running meltano itself, not usually directly for the tap dev. i.e. to run a project pointing to a different database. The guys are working on environments of course, but prior to this the way I currently do that is create separate .env files, and when we run 'meltano elt ...' or whatever in a workspace we're setting the environment too. So typically our 'debug locally' approach is to get the env from our apps workspace, paste into a local .env and invoke...

ahh so you have some kind of "secrets manager" (apps workspace) and you switch them around enough it's easier to pull from the secret manager first