You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by gi...@apache.org on 2020/08/17 23:13:44 UTC

[airflow-site] branch asf-site updated: Update asf-site to output generated at e7e5638

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/airflow-site.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new 87a0b1b  Update asf-site to output generated at e7e5638
87a0b1b is described below

commit 87a0b1b54605b227450d00ef769f037f184e44e0
Author: mik-laj <mi...@users.noreply.github.com>
AuthorDate: Mon Aug 17 23:13:29 2020 +0000

    Update asf-site to output generated at e7e5638
---
 blog/airflow-1.10.10/index.html                    |   4 +-
 blog/airflow-1.10.8-1.10.9/index.html              |   4 +-
 blog/airflow-survey/index.html                     |   4 +-
 blog/announcing-new-website/index.html             |   4 +-
 blog/apache-airflow-for-newcomers/index.html       |  15 +--
 .../index.html                                     |   4 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   4 +-
 .../index.html                                     |   4 +-
 blog/index.xml                                     |   9 +-
 .../index.html                                     |   4 +-
 blog/tags/community/index.xml                      |   9 +-
 index.html                                         |  32 +++----
 index.xml                                          |   9 +-
 search/index.html                                  |   4 +-
 sitemap.xml                                        | 104 ++++++++++-----------
 use-cases/adobe/index.html                         |   4 +-
 use-cases/big-fish-games/index.html                |   4 +-
 use-cases/dish/index.html                          |   4 +-
 use-cases/experity/index.html                      |   4 +-
 use-cases/onefootball/index.html                   |   4 +-
 21 files changed, 105 insertions(+), 133 deletions(-)

diff --git a/blog/airflow-1.10.10/index.html b/blog/airflow-1.10.10/index.html
index 15e3483..e559342 100644
--- a/blog/airflow-1.10.10/index.html
+++ b/blog/airflow-1.10.10/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2020-04-09T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Apache Airflow 1.10.10">
 <meta itemprop="description" content="We are happy to present Apache Airflow 1.10.10">
 
 
 <meta itemprop="datePublished" content="2020-04-09T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="1143">
 
 
diff --git a/blog/airflow-1.10.8-1.10.9/index.html b/blog/airflow-1.10.8-1.10.9/index.html
index b58851b..6a57a43 100644
--- a/blog/airflow-1.10.8-1.10.9/index.html
+++ b/blog/airflow-1.10.8-1.10.9/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2020-02-23T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Apache Airflow 1.10.8 &amp; 1.10.9">
 <meta itemprop="description" content="We are happy to present the new 1.10.8 and 1.10.9 releases of Apache Airflow.">
 
 
 <meta itemprop="datePublished" content="2020-02-23T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="437">
 
 
diff --git a/blog/airflow-survey/index.html b/blog/airflow-survey/index.html
index 138b35f..6477b71 100644
--- a/blog/airflow-survey/index.html
+++ b/blog/airflow-survey/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-12-11T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Airflow Survey 2019">
 <meta itemprop="description" content="Receiving and adjusting to our users’ feedback is a must. Let’s see who Airflow users are, how they play with it, and what they miss.">
 
 
 <meta itemprop="datePublished" content="2019-12-11T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="1775">
 
 
diff --git a/blog/announcing-new-website/index.html b/blog/announcing-new-website/index.html
index 89a3cee..5cdcde8 100644
--- a/blog/announcing-new-website/index.html
+++ b/blog/announcing-new-website/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-12-11T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="New Airflow website">
 <meta itemprop="description" content="We are thrilled about our new website!">
 
 
 <meta itemprop="datePublished" content="2019-12-11T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="282">
 
 
diff --git a/blog/apache-airflow-for-newcomers/index.html b/blog/apache-airflow-for-newcomers/index.html
index 7c27874..c2448ec 100644
--- a/blog/apache-airflow-for-newcomers/index.html
+++ b/blog/apache-airflow-for-newcomers/index.html
@@ -37,15 +37,15 @@ Authoring Workflow in Apache Airflow. Airflow makes it easy to author workflows
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2020-08-17T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Apache Airflow For Newcomers">
 <meta itemprop="description" content="Apache Airflow is a platform to programmatically author, schedule, and monitor workflows. A workflow is a sequence of tasks that processes a set of data. You can think of workflow as the path that describes how tasks go from being undone to done. Scheduling, on the other hand, is the process of planning, controlling, and optimizing when a particular task should be done.
 Authoring Workflow in Apache Airflow. Airflow makes it easy to author workflows using python scripts.">
 
 
 <meta itemprop="datePublished" content="2020-08-17T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
-<meta itemprop="wordCount" content="1107">
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
+<meta itemprop="wordCount" content="1070">
 
 
 
@@ -505,7 +505,7 @@ The metadata database is where the status of all tasks are recorded. The status
 necessary for the task to be executed. It should be noted that the scheduler won&rsquo;t trigger your tasks until
 the period it covers has ended. If a task&rsquo;s <code>schedule_interval</code> is <code>@daily</code>, the scheduler triggers the task
 at the end of the day and not at the beginning. This is to ensure that the necessary data needed for the tasks
-are ready. It is also possible trigger tasks manually on the UI.</p>
+are ready. It is also possible to trigger tasks manually on the UI.</p>
 
 <p>In the <a href="https://github.com/apache/airflow/blob/master/BREEZE.rst" target="_blank">Breeze environment</a>, the scheduler is started by running the command <code>airflow scheduler</code>. It uses
 the configured production environment. The configuration can be specified in <code>airflow.cfg</code></p>
@@ -583,13 +583,6 @@ Just like Operators, there are many predefined sensors in Airflow. These include
 
 <p>A list of most of the available sensors can be found in this <a href="https://airflow.apache.org/docs/stable/_api/airflow/contrib/sensors/index.html?highlight=sensors#module-airflow.contrib.sensors" target="_blank">module</a></p>
 
-<h3 id="breeze-environment-1">Breeze Environment</h3>
-
-<p>The breeze environment is the development environment for Airflow where you can run tests, build images,
-build documentations and so many other things. There are excellent
-<a href="https://github.com/apache/airflow/blob/master/BREEZE.rst" target="_blank">documentation and video</a> on Breeze environment.
-Please check them out.</p>
-
 <h3 id="contributing-to-airflow">Contributing to Airflow</h3>
 
 <p>Airflow is an open source project, everyone is welcome to contribute. It is easy to get started thanks
diff --git a/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html b/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
index 5a62a6e..8b813a6 100644
--- a/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
+++ b/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="ApacheCon Europe 2019 — Thoughts and Insights by Airflow Committers">
 <meta itemprop="description" content="Here come some thoughts by Airflow committers and contributors from the ApacheCon Europe 2019. Get to know the ASF community!">
 
 
 <meta itemprop="datePublished" content="2019-11-22T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="138">
 
 
diff --git a/blog/documenting-using-local-development-environments/index.html b/blog/documenting-using-local-development-environments/index.html
index 0cc344e..e12576a 100644
--- a/blog/documenting-using-local-development-environments/index.html
+++ b/blog/documenting-using-local-development-environments/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Documenting using local development environment">
 <meta itemprop="description" content="The story behind documenting local development environment of Apache Airflow">
 
 
 <meta itemprop="datePublished" content="2019-11-22T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="256">
 
 
diff --git a/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html b/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
index bb8e744..19c2562 100644
--- a/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
+++ b/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/index.html
@@ -37,14 +37,14 @@ About Me I have been writing tech articles on medium as well as my blog for the
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-12-20T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Experience in Google Season of Docs 2019 with Apache Airflow">
 <meta itemprop="description" content="I came across Google Season of Docs (GSoD) almost by accident, thanks to my extensive HackerNews and Twitter addiction. I was familiar with the Google Summer of Code but not with this program. It turns out it was the inaugural phase. I read the details, and the process felt a lot like GSoC except that this was about documentation.
 About Me I have been writing tech articles on medium as well as my blog for the past 1.">
 
 
 <meta itemprop="datePublished" content="2019-12-20T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="1521">
 
 
diff --git a/blog/implementing-stable-api-for-apache-airflow/index.html b/blog/implementing-stable-api-for-apache-airflow/index.html
index c95da00..4fe7c95 100644
--- a/blog/implementing-stable-api-for-apache-airflow/index.html
+++ b/blog/implementing-stable-api-for-apache-airflow/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2020-07-19T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Implementing Stable API for Apache Airflow">
 <meta itemprop="description" content="An Outreachy intern&#39;s progress report on contributing to Apache Airflow REST API.">
 
 
 <meta itemprop="datePublished" content="2020-07-19T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="703">
 
 
diff --git a/blog/index.xml b/blog/index.xml
index 23f150e..82338ad 100644
--- a/blog/index.xml
+++ b/blog/index.xml
@@ -77,7 +77,7 @@ The metadata database is where the status of all tasks are recorded. The status
 necessary for the task to be executed. It should be noted that the scheduler won&amp;rsquo;t trigger your tasks until
 the period it covers has ended. If a task&amp;rsquo;s &lt;code&gt;schedule_interval&lt;/code&gt; is &lt;code&gt;@daily&lt;/code&gt;, the scheduler triggers the task
 at the end of the day and not at the beginning. This is to ensure that the necessary data needed for the tasks
-are ready. It is also possible trigger tasks manually on the UI.&lt;/p&gt;
+are ready. It is also possible to trigger tasks manually on the UI.&lt;/p&gt;
 
 &lt;p&gt;In the &lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;Breeze environment&lt;/a&gt;, the scheduler is started by running the command &lt;code&gt;airflow scheduler&lt;/code&gt;. It uses
 the configured production environment. The configuration can be specified in &lt;code&gt;airflow.cfg&lt;/code&gt;&lt;/p&gt;
@@ -155,13 +155,6 @@ Just like Operators, there are many predefined sensors in Airflow. These include
 
 &lt;p&gt;A list of most of the available sensors can be found in this &lt;a href=&#34;https://airflow.apache.org/docs/stable/_api/airflow/contrib/sensors/index.html?highlight=sensors#module-airflow.contrib.sensors&#34; target=&#34;_blank&#34;&gt;module&lt;/a&gt;&lt;/p&gt;
 
-&lt;h3 id=&#34;breeze-environment-1&#34;&gt;Breeze Environment&lt;/h3&gt;
-
-&lt;p&gt;The breeze environment is the development environment for Airflow where you can run tests, build images,
-build documentations and so many other things. There are excellent
-&lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;documentation and video&lt;/a&gt; on Breeze environment.
-Please check them out.&lt;/p&gt;
-
 &lt;h3 id=&#34;contributing-to-airflow&#34;&gt;Contributing to Airflow&lt;/h3&gt;
 
 &lt;p&gt;Airflow is an open source project, everyone is welcome to contribute. It is easy to get started thanks
diff --git a/blog/its-a-breeze-to-develop-apache-airflow/index.html b/blog/its-a-breeze-to-develop-apache-airflow/index.html
index 0b0f420..9241263 100644
--- a/blog/its-a-breeze-to-develop-apache-airflow/index.html
+++ b/blog/its-a-breeze-to-develop-apache-airflow/index.html
@@ -36,13 +36,13 @@
 
 <meta property="og:image" content="/images/feature-image.png" />
 <meta property="article:published_time" content="2019-11-22T00:00:00+00:00" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="It&#39;s a &#34;Breeze&#34; to develop Apache Airflow">
 <meta itemprop="description" content="A Principal Software Engineer&#39;s journey to developer productivity. Learn how Jarek and his team speeded up and simplified Airflow development for the community.">
 
 
 <meta itemprop="datePublished" content="2019-11-22T00:00:00&#43;00:00" />
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="127">
 
 
diff --git a/blog/tags/community/index.xml b/blog/tags/community/index.xml
index ac9f816..9b549ab 100644
--- a/blog/tags/community/index.xml
+++ b/blog/tags/community/index.xml
@@ -78,7 +78,7 @@ The metadata database is where the status of all tasks are recorded. The status
 necessary for the task to be executed. It should be noted that the scheduler won&amp;rsquo;t trigger your tasks until
 the period it covers has ended. If a task&amp;rsquo;s &lt;code&gt;schedule_interval&lt;/code&gt; is &lt;code&gt;@daily&lt;/code&gt;, the scheduler triggers the task
 at the end of the day and not at the beginning. This is to ensure that the necessary data needed for the tasks
-are ready. It is also possible trigger tasks manually on the UI.&lt;/p&gt;
+are ready. It is also possible to trigger tasks manually on the UI.&lt;/p&gt;
 
 &lt;p&gt;In the &lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;Breeze environment&lt;/a&gt;, the scheduler is started by running the command &lt;code&gt;airflow scheduler&lt;/code&gt;. It uses
 the configured production environment. The configuration can be specified in &lt;code&gt;airflow.cfg&lt;/code&gt;&lt;/p&gt;
@@ -156,13 +156,6 @@ Just like Operators, there are many predefined sensors in Airflow. These include
 
 &lt;p&gt;A list of most of the available sensors can be found in this &lt;a href=&#34;https://airflow.apache.org/docs/stable/_api/airflow/contrib/sensors/index.html?highlight=sensors#module-airflow.contrib.sensors&#34; target=&#34;_blank&#34;&gt;module&lt;/a&gt;&lt;/p&gt;
 
-&lt;h3 id=&#34;breeze-environment-1&#34;&gt;Breeze Environment&lt;/h3&gt;
-
-&lt;p&gt;The breeze environment is the development environment for Airflow where you can run tests, build images,
-build documentations and so many other things. There are excellent
-&lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;documentation and video&lt;/a&gt; on Breeze environment.
-Please check them out.&lt;/p&gt;
-
 &lt;h3 id=&#34;contributing-to-airflow&#34;&gt;Contributing to Airflow&lt;/h3&gt;
 
 &lt;p&gt;Airflow is an open source project, everyone is welcome to contribute. It is easy to get started thanks
diff --git a/index.html b/index.html
index 3432e30..404d82f 100644
--- a/index.html
+++ b/index.html
@@ -1198,12 +1198,12 @@ if (!doNotTrack) {
             <div id="integrations-container" class="list-items">
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#software-integrations">
+                <a class="list-item" href="/docs/stable/integration.html#protocol-integrations">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">MySQL</span>
+        <span class="box-event__integration--name">gRPC</span>
     </div>
 </div>
 
@@ -1211,12 +1211,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#aws-amazon-web-services">
+                <a class="list-item" href="/docs/stable/integration.html#protocol-integrations">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Amazon Simple Storage Service (S3)</span>
+        <span class="box-event__integration--name">Filesystem</span>
     </div>
 </div>
 
@@ -1224,12 +1224,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#service-integrations">
+                <a class="list-item" href="/docs/stable/integration.html#gcp-google-cloud-platform">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Vertica</span>
+        <span class="box-event__integration--name">Cloud Storage (GCS)</span>
     </div>
 </div>
 
@@ -1237,12 +1237,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#service-integrations">
+                <a class="list-item" href="/docs/stable/integration.html#azure-microsoft-azure">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Zendesk</span>
+        <span class="box-event__integration--name">Azure Blob Storage</span>
     </div>
 </div>
 
@@ -1250,12 +1250,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#gcp-google-cloud-platform">
+                <a class="list-item" href="/docs/stable/integration.html#service-integrations">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Storage Transfer Service</span>
+        <span class="box-event__integration--name">Google Drive</span>
     </div>
 </div>
 
@@ -1263,12 +1263,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#aws-amazon-web-services">
+                <a class="list-item" href="/docs/stable/integration.html#gcp-google-cloud-platform">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Amazon EMR</span>
+        <span class="box-event__integration--name">Cloud SQL</span>
     </div>
 </div>
 
@@ -1276,12 +1276,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#aws-amazon-web-services">
+                <a class="list-item" href="/docs/stable/integration.html#protocol-integrations">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Amazon Simple Notification Service (SNS)</span>
+        <span class="box-event__integration--name">Windows Remote Management (WinRM)</span>
     </div>
 </div>
 
@@ -1289,12 +1289,12 @@ if (!doNotTrack) {
                 
                 
                 
-                <a class="list-item" href="/docs/stable/integration.html#service-integrations">
+                <a class="list-item" href="/docs/stable/integration.html#protocol-integrations">
                     
 
 <div class="card">
     <div class="box-event box-event__integration">
-        <span class="box-event__integration--name">Segment</span>
+        <span class="box-event__integration--name">SSH File Transfer Protocol (SFTP)</span>
     </div>
 </div>
 
diff --git a/index.xml b/index.xml
index 9403044..9bef47a 100644
--- a/index.xml
+++ b/index.xml
@@ -76,7 +76,7 @@ The metadata database is where the status of all tasks are recorded. The status
 necessary for the task to be executed. It should be noted that the scheduler won&amp;rsquo;t trigger your tasks until
 the period it covers has ended. If a task&amp;rsquo;s &lt;code&gt;schedule_interval&lt;/code&gt; is &lt;code&gt;@daily&lt;/code&gt;, the scheduler triggers the task
 at the end of the day and not at the beginning. This is to ensure that the necessary data needed for the tasks
-are ready. It is also possible trigger tasks manually on the UI.&lt;/p&gt;
+are ready. It is also possible to trigger tasks manually on the UI.&lt;/p&gt;
 
 &lt;p&gt;In the &lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;Breeze environment&lt;/a&gt;, the scheduler is started by running the command &lt;code&gt;airflow scheduler&lt;/code&gt;. It uses
 the configured production environment. The configuration can be specified in &lt;code&gt;airflow.cfg&lt;/code&gt;&lt;/p&gt;
@@ -154,13 +154,6 @@ Just like Operators, there are many predefined sensors in Airflow. These include
 
 &lt;p&gt;A list of most of the available sensors can be found in this &lt;a href=&#34;https://airflow.apache.org/docs/stable/_api/airflow/contrib/sensors/index.html?highlight=sensors#module-airflow.contrib.sensors&#34; target=&#34;_blank&#34;&gt;module&lt;/a&gt;&lt;/p&gt;
 
-&lt;h3 id=&#34;breeze-environment-1&#34;&gt;Breeze Environment&lt;/h3&gt;
-
-&lt;p&gt;The breeze environment is the development environment for Airflow where you can run tests, build images,
-build documentations and so many other things. There are excellent
-&lt;a href=&#34;https://github.com/apache/airflow/blob/master/BREEZE.rst&#34; target=&#34;_blank&#34;&gt;documentation and video&lt;/a&gt; on Breeze environment.
-Please check them out.&lt;/p&gt;
-
 &lt;h3 id=&#34;contributing-to-airflow&#34;&gt;Contributing to Airflow&lt;/h3&gt;
 
 &lt;p&gt;Airflow is an open source project, everyone is welcome to contribute. It is easy to get started thanks
diff --git a/search/index.html b/search/index.html
index 79f95a2..b20cc35 100644
--- a/search/index.html
+++ b/search/index.html
@@ -35,12 +35,12 @@
 <meta property="og:url" content="/search/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Search Results">
 <meta itemprop="description" content="">
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="0">
 
 
diff --git a/sitemap.xml b/sitemap.xml
index 6f73922..7ffcf99 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,207 +4,207 @@
   
   <url>
     <loc>/docs/overview/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/beds/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/ponycopters/configuring-ponycopters/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/getting-started/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/examples/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/ponycopters/launching-ponycopters/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tutorials/multi-bear/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/porridge/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/concepts/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/task/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tutorials/tutorial2/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tutorials/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/reference/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/contribution-guidelines/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/apache-airflow-for-newcomers/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/community/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/tags/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/announcements/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/implementing-stable-api-for-apache-airflow/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/rest-api/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/airflow-1.10.10/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/release/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/airflow-1.10.8-1.10.9/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/documentation/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/airflow-survey/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/announcing-new-website/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/survey/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/users/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/tags/development/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/documenting-using-local-development-environments/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/its-a-breeze-to-develop-apache-airflow/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/getting-started/example-page/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/reference/parameter-reference/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/docs/tasks/ponycopters/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/adobe/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/big-fish-games/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/blog/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
@@ -213,57 +213,57 @@
   
   <url>
     <loc>/community/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/dish/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/experity/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/install/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/meetups/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/onefootball/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/privacy-notice/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/roadmap/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/search/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
   <url>
     <loc>/use-cases/</loc>
-    <lastmod>2020-08-17T23:23:00+02:00</lastmod>
+    <lastmod>2020-08-18T00:10:03+01:00</lastmod>
   </url>
   
 </urlset>
\ No newline at end of file
diff --git a/use-cases/adobe/index.html b/use-cases/adobe/index.html
index fc43f7c..7d03b7a 100644
--- a/use-cases/adobe/index.html
+++ b/use-cases/adobe/index.html
@@ -35,12 +35,12 @@
 <meta property="og:url" content="/use-cases/adobe/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Adobe">
 <meta itemprop="description" content="What was the problem? Modern big data platforms need sophisticated data pipelines connecting to many backend services enabling complex workflows. These workflows need to be deployed, monitored, and run either on regular schedules or triggered by external events. Adobe Experience Platform component services architected and built an orchestration service to enable their users to author, schedule, and monitor complex hierarchical (including sequential a [...]
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="251">
 
 
diff --git a/use-cases/big-fish-games/index.html b/use-cases/big-fish-games/index.html
index 5848338..e94d143 100644
--- a/use-cases/big-fish-games/index.html
+++ b/use-cases/big-fish-games/index.html
@@ -35,12 +35,12 @@
 <meta property="og:url" content="/use-cases/big-fish-games/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Big Fish Games">
 <meta itemprop="description" content="What was the problem? The main challenge is the lack of standardized ETL workflow orchestration tools. PowerShell and Python-based ETL frameworks built in-house are currently used for scheduling and running analytical workloads. However, there is no web UI through which we can monitor these workflows and it requires additional effort to maintain this framework. These scheduled jobs based on external dependencies are not well suited to modern Big Data [...]
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="336">
 
 
diff --git a/use-cases/dish/index.html b/use-cases/dish/index.html
index 106edd7..4148730 100644
--- a/use-cases/dish/index.html
+++ b/use-cases/dish/index.html
@@ -35,12 +35,12 @@
 <meta property="og:url" content="/use-cases/dish/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Dish">
 <meta itemprop="description" content="What was the problem? We faced increasing complexity managing lengthy crontabs with scheduling being an issue, this required carefully planning timing due to resource constraints, usage patterns, and especially custom code needed for retry logic. In the last case, having to verify success of previous jobs and/or steps prior to running the next. Furthermore, time to results is important, but we were increasingly relying on buffers for processing, wher [...]
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="249">
 
 
diff --git a/use-cases/experity/index.html b/use-cases/experity/index.html
index 22bdd1f..a91263c 100644
--- a/use-cases/experity/index.html
+++ b/use-cases/experity/index.html
@@ -36,13 +36,13 @@ How did Apache Airflow help to solve this problem? Ultimately we decided flexibl
 <meta property="og:url" content="/use-cases/experity/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Experity">
 <meta itemprop="description" content="What was the problem? We had to deploy our complex, flagship app to multiple nodes in multiple ways. This required tasks to communicate across Windows nodes and coordinate timing perfectly. We did not want to buy an expensive enterprise scheduling tool and needed ultimate flexibility.
 How did Apache Airflow help to solve this problem? Ultimately we decided flexible, multi-node, DAG capable tooling was key and airflow was one of the few tools that fit that bill.">
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="191">
 
 
diff --git a/use-cases/onefootball/index.html b/use-cases/onefootball/index.html
index efb545a..4b15d09 100644
--- a/use-cases/onefootball/index.html
+++ b/use-cases/onefootball/index.html
@@ -36,13 +36,13 @@ On top of that, new data tools appear each month: third party data sources, clou
 <meta property="og:url" content="/use-cases/onefootball/" />
 
 <meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2020-08-17T23:23:00+02:00" /><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2020-08-18T00:10:03+01:00" /><meta property="og:site_name" content="Apache Airflow" />
 <meta itemprop="name" content="Onefootball">
 <meta itemprop="description" content="What was the problem? With millions of daily active users, managing the complexity of data engineering at Onefootball is a constant challenge. Lengthy crontabs, multiplication of custom API clients, erosion of confidence in the analytics served, increasing heroism (&ldquo;only one person can solve this issue&rdquo;). Those are the challenges that most teams face unless they consciously invest in their tools and processes.
 On top of that, new data tools appear each month: third party data sources, cloud providers solutions, different storage technologies&hellip; Managing all those integrations is costly and brittle, especially for small data engineering teams that are trying to do more with less.">
 
 
-<meta itemprop="dateModified" content="2020-08-17T23:23:00&#43;02:00" />
+<meta itemprop="dateModified" content="2020-08-18T00:10:03&#43;01:00" />
 <meta itemprop="wordCount" content="294">