hi. i would like to have a specifi branch for an extractor depending on the environnements defined in the meltano.yml file.

Hi @eezec! That’s not currently possible, but a sensible implementation could be to allow expanding env vars in the

pip_url

, so something like

pip_url: git+<https://github.com/meltanolabs/tap-github${TAP_REF}>

would expand with

TAP_REF='#feature-branch'

Yeah, I can see this being helpful. The challenge here implementation-wise is that environments can be swapped with a simple CLI flag, but toggling in and out of environments wouldn't cause a re-install of the related virtual environment where the plugin is installed. @eezec - Can you say a bit more of your use case here, and how many different variants you expect to want to reference simultaneously - in the same project but in different Meltano environments?

i have a local dev env with custom taps being coded these melatno stack is begin built as a docker container called by airflow and i deploy in production these stuff we necessary so all this worflow require to have the same meltano config, customized with env vars and with different branches

@eezec what @edgar_ramirez_mondragon was sharing was a proposed feature request of how we could support this use case. Meltano currently doesn’t unfortunately