<p dir="auto">Hello,</p>
<p dir="auto">The description of some of the commands on the list are too long. This makes them difficult to read.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/12058428/79671178-bd719000-81c8-11ea-97b5-fc4b4aae0abf.png"><img width="726" alt="Screenshot 2020-04-18 at 23 02 43" src="https://user-images.githubusercontent.com/12058428/79671178-bd719000-81c8-11ea-97b5-fc4b4aae0abf.png" style="max-width: 100%;"></a></p>
<p dir="auto">I think that some text should be moved to descriptions of individual commands e.g. `airflow days backfill --help<code class="notranslate">. We currently do not have descriptions for individual commands. After executing the </code> --help '' command, we only have a list of arguments.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/12058428/79671219-248f4480-81c9-11ea-8b6c-030495e3be86.png"><img width="720" alt="Screenshot 2020-04-18 at 23 04 40" src="https://user-images.githubusercontent.com/12058428/79671219-248f4480-81c9-11ea-8b6c-030495e3be86.png" style="max-width: 100%;"></a></p>
<p dir="auto">After making changes it may look like the screen below.<br>
<a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/12058428/79671262-8059cd80-81c9-11ea-8539-dee59122c511.png"><img width="720" alt="Screenshot 2020-04-18 at 23 08 11" src="https://user-images.githubusercontent.com/12058428/79671262-8059cd80-81c9-11ea-8539-dee59122c511.png" style="max-width: 100%;"></a></p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://user-images.githubusercontent.com/12058428/79671338-e5152800-81c9-11ea-9f3a-1f28628d6af5.png"><img width="729" alt="Screenshot 2020-04-18 at 23 10 58" src="https://user-images.githubusercontent.com/12058428/79671338-e5152800-81c9-11ea-9f3a-1f28628d6af5.png" style="max-width: 100%;"></a></p>
<p dir="auto">Descriptions can be set by the parameters <code class="notranslate">description</code> or<code class="notranslate"> epilogue</code>.<br>
</p><div class="Box Box--condensed my-2">
  <div class="Box-header f6">
    <p class="mb-0 text-bold">
      <a href="https://github.com/apache/airflow/blob/8517cb189872aebdd70e9d5d584478cd7fb65d0f/airflow/cli/cli_parser.py#L1280-L1282">airflow/airflow/cli/cli_parser.py</a>
    </p>
    <p class="mb-0 color-fg-muted">
        Lines 1280 to 1282
      in
      <a data-pjax="true" class="commit-tease-sha" href="/apache/airflow/commit/8517cb189872aebdd70e9d5d584478cd7fb65d0f">8517cb1</a>
    </p>
  </div>
  <div itemprop="text" class="Box-body p-0 blob-wrapper blob-wrapper-embedded data">
    <table class="highlight tab-size mb-0 js-file-line-container" data-tab-size="8" data-paste-markdown-skip="">

        <tbody><tr class="border-0">
          <td id="L1280" class="blob-num border-0 px-3 py-0 color-bg-default" data-line-number="1280"></td>
          <td id="LC1280" class="blob-code border-0 px-3 py-0 color-bg-default blob-code-inner js-file-line"> <span class="pl-s1">sub_proc</span> <span class="pl-c1">=</span> <span class="pl-s1">subparsers</span>.<span class="pl-en">add_parser</span>( </td>
        </tr>

        <tr class="border-0">
          <td id="L1281" class="blob-num border-0 px-3 py-0 color-bg-default" data-line-number="1281"></td>
          <td id="LC1281" class="blob-code border-0 px-3 py-0 color-bg-default blob-code-inner js-file-line">     <span class="pl-s1">sub</span>.<span class="pl-s1">name</span>, <span class="pl-s1">help</span><span class="pl-c1">=</span><span class="pl-s1">sub</span>.<span class="pl-s1">help</span> </td>
        </tr>

        <tr class="border-0">
          <td id="L1282" class="blob-num border-0 px-3 py-0 color-bg-default" data-line-number="1282"></td>
          <td id="LC1282" class="blob-code border-0 px-3 py-0 color-bg-default blob-code-inner js-file-line"> ) </td>
        </tr>
    </tbody></table>
  </div>
</div>
<p></p>
<div class="highlight highlight-source-diff notranslate position-relative overflow-auto" dir="auto" data-snippet-clipboard-copy-content="    sub_proc = subparsers.add_parser(
-        sub.name, help=sub.help
+        sub.name, help=sub.help, description=&quot;DESCRIPTION&quot;, epilog=&quot;EPILOG&quot;
    )"><pre class="notranslate">    sub_proc = subparsers.add_parser(
<span class="pl-md"><span class="pl-md">-</span>        sub.name, help=sub.help</span>
<span class="pl-mi1"><span class="pl-mi1">+</span>        sub.name, help=sub.help, description="DESCRIPTION", epilog="EPILOG"</span>
    )</pre></div>
<p dir="auto">I would be happy if all the commands had a description. It may duplicate the description from the list.</p>
<h3 dir="auto">Description</h3>
<p dir="auto">I think adding the following operators/sensors would benefit companies that need to start/stop RDS instances programmatically.</p>
<table role="table">
<thead>
<tr>
<th align="left">Name</th>
<th align="left">Description</th>
<th align="left">PR</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code class="notranslate">RdsStartDbOperator</code></td>
<td align="left">Start an instance, and optionally wait for it enter "available" state</td>
<td align="left"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1410382201" data-permission-text="Title is private" data-url="https://github.com/apache/airflow/issues/27076" data-hovercard-type="pull_request" data-hovercard-url="/apache/airflow/pull/27076/hovercard" href="https://github.com/apache/airflow/pull/27076">#27076</a></td>
</tr>
<tr>
<td align="left"><code class="notranslate">RdsStopDbOperator</code></td>
<td align="left">Start an instance, and optionally wait for it to enter "stopped" state</td>
<td align="left"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1410382201" data-permission-text="Title is private" data-url="https://github.com/apache/airflow/issues/27076" data-hovercard-type="pull_request" data-hovercard-url="/apache/airflow/pull/27076/hovercard" href="https://github.com/apache/airflow/pull/27076">#27076</a></td>
</tr>
<tr>
<td align="left"><code class="notranslate">RdsDbSensor</code></td>
<td align="left">Wait for the requested status (eg. available, stopped)</td>
<td align="left"><a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="1352964025" data-permission-text="Title is private" data-url="https://github.com/apache/airflow/issues/26003" data-hovercard-type="pull_request" data-hovercard-url="/apache/airflow/pull/26003/hovercard" href="https://github.com/apache/airflow/pull/26003">#26003</a></td>
</tr>
</tbody>
</table>
<p dir="auto">Is this something that would be accepted into the codebase?<br>
Please let me know.</p>
<h3 dir="auto">Use case/motivation</h3>
<h4 dir="auto">1. Saving money</h4>
<p dir="auto">RDS is expensive. To save money, a company keeps test/dev environment relational databases shutdown until it needs to use them. With Airflow, they can start a database instance before running a workload, then turn it off after the workload finishes (or errors).</p>
<h4 dir="auto">2. Force RDS to stay shutdown</h4>
<p dir="auto">RDS automatically starts a database after 1 week of downtime. A company does not need this feature. They can create a DAG to continuously run the shutdown command on a list of databases instance ids stored in a <code class="notranslate">Variable</code>. The alternative is to create a shell script or login to the console and manually shutdown each database every week.</p>
<h4 dir="auto">3. Making sure a database is running before scheduling workload</h4>
<p dir="auto">A company programmatically starts/stops its RDS instances. Before they run a workload, they want to make sure it's running. They can use a sensor to make sure a database is available before attempting to run any jobs that require access.</p>
<p dir="auto">Also, during maintenance windows, RDS instances may be taken offline. Rather than tuning each DAG schedule to run outside of this window, a company can use a sensor to wait until the instance is available. (Yes, the availability check could also take place immediately before the maintenance window.)</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" checked=""> 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>