<h3 dir="auto">Description</h3>
<p dir="auto">I find the connections view often leads to confusion because connections defined as environment variables and in a secrets backend are not displayed. This is not stated clearly.</p>
<p dir="auto">I suggest to:</p>
<ol dir="auto">
<li>Display connections set via environment variables (and hide the edit controls for those connections). This could also help debugging a URI string if you could see the URI components broken down in the connection view.</li>
<li>Display an info message in the connections view in case a secrets backend is configured stating that those connections are not visible in the webserver.</li>
</ol>
<h3 dir="auto">Use case/motivation</h3>
<p dir="auto">Motivation: having to explain over and over that <em>only</em> connections defined in the Airflow metastore are visible in the webserver.</p>
<h3 dir="auto">Related issues</h3>
<p dir="auto"><em>No response</em></p>
<h3 dir="auto">Are you willing to submit a PR?</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox"> Yes I am willing to submit a PR!</li>
</ul>
<h3 dir="auto">Code of Conduct</h3>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I agree to follow this project's <a href="https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md">Code of Conduct</a></li>
</ul>
<p dir="auto"><strong>Apache Airflow version</strong>: 1.10.9</p>
<p dir="auto"><strong>Environment</strong>:</p>
<ul dir="auto">
<li><strong>Cloud provider or hardware configuration</strong>:</li>
<li><strong>OS</strong> (e.g. from /etc/os-release): ubuntu 18.04</li>
<li><strong>Kernel</strong> (e.g. <code class="notranslate">uname -a</code>):</li>
<li><strong>Install tools</strong>:</li>
<li><strong>Others</strong>:</li>
</ul>
<p dir="auto"><strong>What happened</strong>: Eventlet with CeleryExecutor not working in Airflow 1.10.9 version<br>
<a href="https://github.com/apache/airflow/files/4472893/log.txt">log.txt</a><br>
I notice when I tried switching celery pool option to eventlet the worker doesn’t seem to be picking up tasks.</p>
<p dir="auto">Attached the snippet of logs.</p>

<p dir="auto"><strong>What you expected to happen</strong>:</p>

<p dir="auto"><strong>How to reproduce it</strong>: Start the airflow celery workers with Eventlet</p>

<p dir="auto"><strong>Anything else we need to know</strong>: Attached the logs</p>