potiuk edited a comment on pull request #10873: URL: https://github.com/apache/airflow/pull/10873#issuecomment-695827245
> Descriptions are only useful in the Web UI, and connections from the secret backends are not visible in Airflow, so it is not necessary to add support for this field in the backend secret. Recently there was a discussion about showing the "names" but not "values" of the connections - so that we can see the connections in the UI even if they are coming from the secret backend. I think for 2.0 we should consciously decide what we do with the connection coming from the secrets and potentially show them in the UI. Otherwise it might be very misleading - the user sees a different "reality" than is "viewed" by the workers. I believe if we want to add a new "property" of connection - it is very much related to what we are going to do with displaying them in UI (including secret backends) WDYT @mik-laj - is it good that we do not see secret backend connection, and when we have the connection in db, we see a wrong one ? I think it's rather bad and might be super-confusing for the user. That's why I think we should first decide what we want to do with the connections and later think about adding new properties to them. ---------------------------------------------------------------- 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]
