josh-fell commented on PR #22938: URL: https://github.com/apache/airflow/pull/22938#issuecomment-1126284990
> @josh-fell It is not possible that a single API key could access a single tenant instance + a multi-tenant instance. Each instance will require its own API key So if users will always need to use a separate connection for each API key they want to use because said key can't cross-pollinate with other instances, it seems like the move is to have tenant optionally configurable in the connection rather than overriding at the task level. If it's not populated in the connection, then it's assumed to be a multi-tenant instance which always has a "cloud" tenant name. Am I in the ballpark with that? Or what is a good use case to have the override at the task level? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
