potiuk commented on issue #16952: URL: https://github.com/apache/airflow/issues/16952#issuecomment-882074965
I am with @kaxil on this one. I like the idea of being able to "pin" secret backend specifically as then it pushes the behaviour change and resulting complexity down to DAG developers - not even to "ops" people of the whole Airflow (so that they deal with consequences but are also in full control of it). I think more complexity in configuration and ability to swap things around might create far too much confusion if done at the "configuration" level for the whole Airfloow, even more so when in the future we would like to add multi-tenancy features (that feature sounds like something that poeple would ask their ops people to configure differently for different teams, and resulting troubleshooting might quickly spin out of control if we allow more flexibility here. I really prefer the situation we have now where we have only one opinionated "sequence" that is supported. At the same time you can write the "Composed" backend easily with your own logic, and - even in multi-tenant cases - each team could have their own custom "Composed" backend if needed likely in multi-tenant scenario rather easily (we could select custom backend per-tenant in configuration). That sounds much more future-proof IMHO regarding configuration and maintenance complexity. -- 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]
