nathadfield commented on pull request #15013:
URL: https://github.com/apache/airflow/pull/15013#issuecomment-810025532


   > There is a benefit inherent in having only one perfectly good way to do 
things.
   > 
   > Sometimes when you want to do something another way it's best kept in a 
private repo for your company or posted on a blog.
   > 
   > I would be in favor of only using the airflow conn uri format. But let's 
see what others think -- I'm just one voice here so don't be too discouraged.
   > 
   > In the meantime I encourage you to try the uri generation function we 
have. There is documentation on generating the uri in the managing connections 
doc.
   
   @dstandish Sure, I take your point but it is also nice to have options.
   
   For the record, I have tried the `conn_uri` method.  Its fine but it does 
require a certain level of knowledge in order to create one.  There are a 
certain category of users who may only ever interact with the Airflow UI but 
may also need to update a secret used by a connection.


-- 
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:
[email protected]


Reply via email to