Taragolis commented on PR #23560: URL: https://github.com/apache/airflow/pull/23560#issuecomment-1124357318
@dstandish I thought about custom mixin secret backend which allow to use different existed secret backends initially. And found that implements prioritisation much easier rather than move all logic to newly created class. Especially I do not know how it would work with `_SECRET` configurations Example: need create secret backend which mixin Env and AWS SSM, what happen when we try to find `awesome_variable` or `super_connection_id` which only defined in Metastore: 1. Check in ENV (Alternative Backend) 2. Check in SSM (Alternative Backend) 3. Check in ENV (Default Backend) 4. Check in Metastore (Default Backend) Another sample, implement custom backend which mixin Env, Metastore, SSM (in this order), in this case we call if variable/connection undefined 1. Check in ENV (Alternative Backend) 2. Check in Metastore (Alternative Backend) 3. Check in SSM (Alternative Backend) 4. Check in ENV (Default Backend) 5. Check in Metastore (Default Backend) About flexible / explicit I have probably couple questions: * Should it allow to users turn off some default backends at all? * Should it allow to users define more than one alternate backends? -- 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]
