josh-fell opened a new pull request #19792:
URL: https://github.com/apache/airflow/pull/19792


   The current implementation of the Test Connection button in the UI is either 
enabled/disabled relative only to the enablement of Airflow REST APIs within an 
environment. Meaning if REST APIs are enabled, the Test Connection button is 
enabled for _all_ connection types even if a selected type doesn't actually 
support testing connectivity in this way. This can be confusing for users.
   
   This PR adds functionality to dynamically enable (or disable) the Test 
Connection button based on if the selected connection type supports testing via 
the Airflow REST API. (Note that if Airflow REST APIs are disabled for an 
environment, this configuration will take precedence over this logic.) Also, 
when disabling the button, the element will now be functionally disabled rather 
than just the appearance of being disabled.
   
   **Example of dynamically disabled Test Connection button:**
   
![image](https://user-images.githubusercontent.com/48934154/143132472-27d9edfe-5726-40b4-8969-e4b828f79b5e.png)
   
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to