dstandish edited a comment on issue #6376: [WIP] [AIRFLOW-5705] Add creds backend classes including AWS SSM URL: https://github.com/apache/airflow/pull/6376#issuecomment-565763910 @mik-laj @ashb what do you think about this one? now that #6440 (cloud sql dynamic conn generation fix) is merged, there's nothing really standing in the way of this one, except for considerations of whether this is right structure. Some example use cases... 1. temporary dev / test cluster: with astronomer, it's easy to spin up new clusters. so for testing something, or special backfill job we can easily create temporary dev cluster. with this change, we would not have to worry about getting connections into cluster. with one env var, or appropriate IAM, the connection info would be available. 2. sharing creds with developers i assume it is common for developers to have connections store in a file like `connections.env.sh` and then sourced in `.bashrc`. Maybe they _also_ have to have them in `.env` file if they also use docker. maybe other folks manage `airflow connections -a` scripts. this change could eliminate all of that by centralizing creds storage and allowing developers to pull from the same source. depending on the service, creds could potentially be versioned. creds changes would be synchronized for everyone. do you think this needs an AIP? if so can i have access to create (apache jira username is dstandish)? do you have any feedback on current structure? i understand that exactly _how_ we do this is probably more controversial than the general idea of opening up creds sourcing.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
