Has anyone got any thoughts on the idea of passing an

Authorization

header to the

MELTANO_DISCOVERY_URL

? We have a dynamically generated

discovery.yml

sitting behind an authorised API endpoint, and would like to be able to point a Meltano project at this when running in a non-interactive environment. Doing something like

curl -H <auth-header> $MELTANO_DISCOVERY_URL > discovery.yml

every time seems like an unnecessary solution.

@Reuben (Matatika) I agree that’s a use case we can support better out of the box. If you file an issue, I think we would take a contribution to add a

discovery_url_authorization

setting (or something to that effect)

Awesome! I’ll create the issue now and probably start an MR too.