This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch gh-pages
in repository https://gitbox.apache.org/repos/asf/airflow-site.git
The following commit(s) were added to refs/heads/gh-pages by this push:
new 7148b92 Deploying to gh-pages from @
2c887ee6fbd22e1e58feb71e386487d92688392e 🚀
7148b92 is described below
commit 7148b92be602634f69f3456ad52f906d00eed509
Author: potiuk <[email protected]>
AuthorDate: Mon Jul 12 20:37:07 2021 +0000
Deploying to gh-pages from @ 2c887ee6fbd22e1e58feb71e386487d92688392e 🚀
---
blog/airflow-1.10.10/index.html | 4 +-
blog/airflow-1.10.12/index.html | 4 +-
blog/airflow-1.10.8-1.10.9/index.html | 4 +-
blog/airflow-survey-2020/index.html | 4 +-
blog/airflow-survey/index.html | 4 +-
blog/airflow-two-point-oh-is-here/index.html | 4 +-
blog/airflow_summit_2021/index.html | 4 +-
blog/announcing-new-website/index.html | 4 +-
blog/apache-airflow-for-newcomers/index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
.../index.html | 4 +-
docs/docker-stack/_sources/entrypoint.rst.txt | 21 +++++-
docs/docker-stack/build.html | 4 +-
docs/docker-stack/entrypoint.html | 23 +++++-
docs/docker-stack/searchindex.js | 2 +-
index.html | 30 ++++----
search/index.html | 4 +-
sitemap.xml | 86 +++++++++++-----------
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 +-
use-cases/plarium-krasnodar/index.html | 4 +-
use-cases/sift/index.html | 4 +-
29 files changed, 147 insertions(+), 111 deletions(-)
diff --git a/blog/airflow-1.10.10/index.html b/blog/airflow-1.10.10/index.html
index 889d1be..e1eb623 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="1143">
diff --git a/blog/airflow-1.10.12/index.html b/blog/airflow-1.10.12/index.html
index 61656c6..f4666d1 100644
--- a/blog/airflow-1.10.12/index.html
+++ b/blog/airflow-1.10.12/index.html
@@ -36,13 +36,13 @@
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2020-08-25T00:00:00+00:00" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.12">
<meta itemprop="description" content="We are happy to present Apache Airflow
1.10.12">
<meta itemprop="datePublished" content="2020-08-25T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="911">
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 e6ab8d3..91c601f 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 1.10.8 & 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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="437">
diff --git a/blog/airflow-survey-2020/index.html
b/blog/airflow-survey-2020/index.html
index 06ce14a..14b220b 100644
--- a/blog/airflow-survey-2020/index.html
+++ b/blog/airflow-survey-2020/index.html
@@ -36,13 +36,13 @@
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2021-03-09T00:00:00+00:00" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Survey 2020">
<meta itemprop="description" content="We observe steady growth in number of
users as well as in an amount of active contributors. So listening and
understanding our community is of high importance.">
<meta itemprop="datePublished" content="2021-03-09T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="2106">
diff --git a/blog/airflow-survey/index.html b/blog/airflow-survey/index.html
index a2a3813..7d2b4a6 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="1775">
diff --git a/blog/airflow-two-point-oh-is-here/index.html
b/blog/airflow-two-point-oh-is-here/index.html
index ecc4d28..3460b25 100644
--- a/blog/airflow-two-point-oh-is-here/index.html
+++ b/blog/airflow-two-point-oh-is-here/index.html
@@ -36,13 +36,13 @@
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2020-12-17T00:00:00+00:00" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Apache Airflow 2.0 is here!">
<meta itemprop="description" content="We're proud to announce that Apache
Airflow 2.0.0 has been released.">
<meta itemprop="datePublished" content="2020-12-17T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="1166">
diff --git a/blog/airflow_summit_2021/index.html
b/blog/airflow_summit_2021/index.html
index c16c488..2c07144 100644
--- a/blog/airflow_summit_2021/index.html
+++ b/blog/airflow_summit_2021/index.html
@@ -36,13 +36,13 @@
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2021-03-21T00:00:00+00:00" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Airflow Summit 2021">
<meta itemprop="description" content="We are thrilled about Airflow Summit
2021!">
<meta itemprop="datePublished" content="2021-03-21T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="77">
diff --git a/blog/announcing-new-website/index.html
b/blog/announcing-new-website/index.html
index 3375118..97dc9c7 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02: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 f36bac2..fea8ba5 100644
--- a/blog/apache-airflow-for-newcomers/index.html
+++ b/blog/apache-airflow-for-newcomers/index.html
@@ -37,14 +37,14 @@ 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="1070">
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 97a80ba..634ef03 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02: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 4015460..f57fbe0 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02: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 4aa05a7..af98a8f 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="1521">
diff --git a/blog/experience-with-airflow-as-an-outreachy-intern/index.html
b/blog/experience-with-airflow-as-an-outreachy-intern/index.html
index 72a4bb7..ffacf44 100644
--- a/blog/experience-with-airflow-as-an-outreachy-intern/index.html
+++ b/blog/experience-with-airflow-as-an-outreachy-intern/index.html
@@ -37,14 +37,14 @@ Contribution Period The first thing I had to do was choose
a project under an or
<meta property="og:image" content="/images/feature-image.png" />
<meta property="article:published_time" content="2020-08-30T00:00:00+00:00" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Journey with Airflow as an Outreachy Intern">
<meta itemprop="description" content="Outreachy is a program which organises
three months paid internships with FOSS projects for people who are typically
underrepresented in those projects.
Contribution Period The first thing I had to do was choose a project under an
organisation. After going through all the projects I chose “Extending the REST
API of Apache Airflow”, because I had a good idea of what REST API(s) are, so I
thought it would be easier to get started with the contributions.">
<meta itemprop="datePublished" content="2020-08-30T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="532">
diff --git a/blog/implementing-stable-api-for-apache-airflow/index.html
b/blog/implementing-stable-api-for-apache-airflow/index.html
index a96ff0f..401a0c4 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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's progress
report on contributing to Apache Airflow REST API.">
<meta itemprop="datePublished" content="2020-07-19T00:00:00+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="703">
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 5d9a081..aa7a2ae 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="It's a "Breeze" to develop Apache
Airflow">
<meta itemprop="description" content="A Principal Software Engineer'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+00:00" />
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="124">
diff --git a/docs/docker-stack/_sources/entrypoint.rst.txt
b/docs/docker-stack/_sources/entrypoint.rst.txt
index c386a67..9438314 100644
--- a/docs/docker-stack/_sources/entrypoint.rst.txt
+++ b/docs/docker-stack/_sources/entrypoint.rst.txt
@@ -262,11 +262,28 @@ and Admin role. They also forward local port ``8080`` to
the webserver port and
Installing additional requirements
..................................
+.. warning:: Installing requirements this way is a very convenient method of
running Airflow, very useful for
+ testing and debugging. However, do not be tricked by its convenience. You
should never, ever use it in
+ production environment. We have deliberately chose to make it a
development/test dependency and we print
+ a warning, whenever it is used. There is an inherent security-related
issue with using this method in
+ production. Installing the requirements this way can happen at literally
any time - when your containers
+ get restarted, when your machines in K8S cluster get restarted. In a K8S
Cluster those events can happen
+ literally any time. This opens you up to a serious vulnerability where
your production environment
+ might be brought down by a single dependency being removed from PyPI - or
even dependency of your
+ dependency. This means that you put your production service availability
in hands of 3rd-party developers.
+ At any time, any moment including weekends and holidays those 3rd party
developers might bring your
+ production Airflow instance down, without you even knowing it. This is a
serious vulnerability that
+ is similar to the infamous
+ `leftpad
<https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code/>`_
+ problem. You can fully protect against this case by building your own,
immutable custom image, where the
+ dependencies are baked in. You have been warned.
+
Installing additional requirements can be done by specifying
``_PIP_ADDITIONAL_REQUIREMENTS`` variable.
The variable should contain a list of requirements that should be installed
additionally when entering
the containers. Note that this option slows down starting of Airflow as every
time any container starts
-it must install new packages. Therefore this option should only be used for
testing. When testing is
-finished, you should create your custom image with dependencies baked in.
+it must install new packages and it opens up huge potential security
vulnerability when used in production
+(see below). Therefore this option should only be used for testing. When
testing is finished,
+you should create your custom image with dependencies baked in.
Example:
diff --git a/docs/docker-stack/build.html b/docs/docker-stack/build.html
index 27cf1a4..4d165cb 100644
--- a/docs/docker-stack/build.html
+++ b/docs/docker-stack/build.html
@@ -1283,7 +1283,7 @@ to provide this library from you repository if you want
to build Airflow image i
<div class="highlight-bash notranslate"><div
class="highlight"><pre><span></span>rm docker-context-files/*.whl
docker-context-files/*.tar.gz docker-context-files/*.txt <span
class="o">||</span> <span class="nb">true</span>
curl -Lo <span
class="s2">"docker-context-files/constraints-3.7.txt"</span> <span
class="se">\</span>
-
https://raw.githubusercontent.com/apache/airflow/constraints-2.0.2/constraints-3.7.txt
+
https://raw.githubusercontent.com/apache/airflow/constraints-2.1.0/constraints-3.7.txt
<span class="c1"># For Airflow pre 2.1 you need to use PIP 20.2.4 to
install/download Airflow packages.</span>
pip install <span class="nv">pip</span><span class="o">==</span><span
class="m">20</span>.2.4
@@ -1323,7 +1323,7 @@ to the below:</p>
<div class="highlight-bash notranslate"><div
class="highlight"><pre><span></span>docker build . <span class="se">\</span>
--build-arg <span class="nv">PYTHON_BASE_IMAGE</span><span
class="o">=</span><span class="s2">"python:3.7-slim-buster"</span>
<span class="se">\</span>
--build-arg <span class="nv">AIRFLOW_INSTALLATION_METHOD</span><span
class="o">=</span><span class="s2">"apache-airflow"</span> <span
class="se">\</span>
- --build-arg <span class="nv">AIRFLOW_VERSION</span><span
class="o">=</span><span class="s2">"2.0.2"</span> <span
class="se">\</span>
+ --build-arg <span class="nv">AIRFLOW_VERSION</span><span
class="o">=</span><span class="s2">"2.1.0"</span> <span
class="se">\</span>
--build-arg <span class="nv">INSTALL_MYSQL_CLIENT</span><span
class="o">=</span><span class="s2">"false"</span> <span
class="se">\</span>
--build-arg <span class="nv">AIRFLOW_PRE_CACHED_PIP_PACKAGES</span><span
class="o">=</span><span class="s2">"false"</span> <span
class="se">\</span>
--build-arg <span class="nv">INSTALL_FROM_DOCKER_CONTEXT_FILES</span><span
class="o">=</span><span class="s2">"true"</span> <span
class="se">\</span>
diff --git a/docs/docker-stack/entrypoint.html
b/docs/docker-stack/entrypoint.html
index 771dda6..0d5f3c3 100644
--- a/docs/docker-stack/entrypoint.html
+++ b/docs/docker-stack/entrypoint.html
@@ -805,11 +805,30 @@ and Admin role. They also forward local port <code
class="docutils literal notra
</div>
<div class="section" id="installing-additional-requirements">
<h3>Installing additional requirements<a class="headerlink"
href="#installing-additional-requirements" title="Permalink to this
headline">¶</a></h3>
+<div class="admonition warning">
+<p class="admonition-title">Warning</p>
+<p>Installing requirements this way is a very convenient method of running
Airflow, very useful for
+testing and debugging. However, do not be tricked by its convenience. You
should never, ever use it in
+production environment. We have deliberately chose to make it a
development/test dependency and we print
+a warning, whenever it is used. There is an inherent security-related issue
with using this method in
+production. Installing the requirements this way can happen at literally any
time - when your containers
+get restarted, when your machines in K8S cluster get restarted. In a K8S
Cluster those events can happen
+literally any time. This opens you up to a serious vulnerability where your
production environment
+might be brought down by a single dependency being removed from PyPI - or even
dependency of your
+dependency. This means that you put your production service availability in
hands of 3rd-party developers.
+At any time, any moment including weekends and holidays those 3rd party
developers might bring your
+production Airflow instance down, without you even knowing it. This is a
serious vulnerability that
+is similar to the infamous
+<a class="reference external"
href="https://qz.com/646467/how-one-programmer-broke-the-internet-by-deleting-a-tiny-piece-of-code/";>leftpad</a>
+problem. You can fully protect against this case by building your own,
immutable custom image, where the
+dependencies are baked in. You have been warned.</p>
+</div>
<p>Installing additional requirements can be done by specifying <code
class="docutils literal notranslate"><span
class="pre">_PIP_ADDITIONAL_REQUIREMENTS</span></code> variable.
The variable should contain a list of requirements that should be installed
additionally when entering
the containers. Note that this option slows down starting of Airflow as every
time any container starts
-it must install new packages. Therefore this option should only be used for
testing. When testing is
-finished, you should create your custom image with dependencies baked in.</p>
+it must install new packages and it opens up huge potential security
vulnerability when used in production
+(see below). Therefore this option should only be used for testing. When
testing is finished,
+you should create your custom image with dependencies baked in.</p>
<p>Example:</p>
<div class="highlight-bash notranslate"><div
class="highlight"><pre><span></span>docker run -it -p <span
class="m">8080</span>:8080 <span class="se">\</span>
--env <span class="s2">"_PIP_ADDITIONAL_REQUIREMENTS=lxml==4.6.3
charset-normalizer==1.4.1"</span> <span class="se">\</span>
diff --git a/docs/docker-stack/searchindex.js b/docs/docker-stack/searchindex.js
index 4ef34de..454396f 100644
--- a/docs/docker-stack/searchindex.js
+++ b/docs/docker-stack/searchindex.js
@@ -1 +1 @@
-Search.setIndex({docnames:["build","build-arg-ref","entrypoint","index","recipes"],envversion:{"sphinx.domains.c":2,"sphinx.domains.changeset":1,"sphinx.domains.citation":1,"sphinx.domains.cpp":3,"sphinx.domains.index":1,"sphinx.domains.javascript":2,"sphinx.domains.math":2,"sphinx.domains.python":2,"sphinx.domains.rst":2,"sphinx.domains.std":1,"sphinx.ext.intersphinx":1,"sphinx.ext.viewcode":1,sphinx:56},filenames:["build.rst","build-arg-ref.rst","entrypoint.rst","index.rst","recipes.rs
[...]
\ No newline at end of file
+Search.setIndex({docnames:["build","build-arg-ref","entrypoint","index","recipes"],envversion:{"sphinx.domains.c":2,"sphinx.domains.changeset":1,"sphinx.domains.citation":1,"sphinx.domains.cpp":3,"sphinx.domains.index":1,"sphinx.domains.javascript":2,"sphinx.domains.math":2,"sphinx.domains.python":2,"sphinx.domains.rst":2,"sphinx.domains.std":1,"sphinx.ext.intersphinx":1,"sphinx.ext.viewcode":1,sphinx:56},filenames:["build.rst","build-arg-ref.rst","entrypoint.rst","index.rst","recipes.rs
[...]
\ No newline at end of file
diff --git a/index.html b/index.html
index c383c9d..af36840 100644
--- a/index.html
+++ b/index.html
@@ -1227,12 +1227,12 @@ if (!doNotTrack) {
<div id="integrations-container" class="list-items">
- <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-docker/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Amazon Redshift</span>
+ <span class="box-event__integration--name">Docker Swarm</span>
</div>
</div>
@@ -1245,7 +1245,7 @@ if (!doNotTrack) {
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">AWS Step Functions</span>
+ <span class="box-event__integration--name">Amazon ElastiCache</span>
</div>
</div>
@@ -1253,12 +1253,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/cloud/datafusion.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Data Fusion</span>
+ <span class="box-event__integration--name">Amazon Web Services</span>
</div>
</div>
@@ -1266,12 +1266,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-salesforce/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Data Proc</span>
+ <span class="box-event__integration--name">Salesforce</span>
</div>
</div>
@@ -1279,12 +1279,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/ads.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-google/stable/operators/marketing_platform/campaign_manager.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Google Ads</span>
+ <span class="box-event__integration--name">Google Campaign
Manager</span>
</div>
</div>
@@ -1292,12 +1292,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-docker/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-zendesk/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Docker Swarm</span>
+ <span class="box-event__integration--name">Zendesk</span>
</div>
</div>
@@ -1305,12 +1305,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-hashicorp/stable/index.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-microsoft-azure/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Hashicorp Vault</span>
+ <span class="box-event__integration--name">Microsoft Azure Data
Explorer</span>
</div>
</div>
@@ -1318,12 +1318,12 @@ if (!doNotTrack) {
- <a class="list-item"
href="/docs/apache-airflow-providers-amazon/stable/operators/ecs.html">
+ <a class="list-item"
href="/docs/apache-airflow-providers-cncf-kubernetes/stable/index.html">
<div class="card">
<div class="box-event box-event__integration">
- <span class="box-event__integration--name">Amazon Simple Email Service
(SES)</span>
+ <span class="box-event__integration--name">Spark on Kubernetes</span>
</div>
</div>
diff --git a/search/index.html b/search/index.html
index 3624318..3a3ad0e 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Search Results">
<meta itemprop="description" content="">
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="0">
diff --git a/sitemap.xml b/sitemap.xml
index d4a449f..935e9c3 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -4,147 +4,147 @@
<url>
<loc>/docs/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/airflow-summit/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow_summit_2021/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/community/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/tags/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-survey-2020/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/survey/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/users/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-two-point-oh-is-here/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/release/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/experience-with-airflow-as-an-outreachy-intern/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-1.10.12/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/apache-airflow-for-newcomers/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/announcements/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/implementing-stable-api-for-apache-airflow/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/rest-api/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-1.10.10/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-1.10.8-1.10.9/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/documentation/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/experience-in-google-season-of-docs-2019-with-apache-airflow/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/airflow-survey/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/announcing-new-website/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/apache-con-europe-2019-thoughts-and-insights-by-airflow-committers/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/tags/development/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/documenting-using-local-development-environments/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/its-a-breeze-to-develop-apache-airflow/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/adobe/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/big-fish-games/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/blog/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
@@ -153,72 +153,72 @@
<url>
<loc>/community/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/dish/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/ecosystem/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/experity/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/install/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/meetups/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/onefootball/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/plarium-krasnodar/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/privacy-notice/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/roadmap/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/search/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/sift/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02:00</lastmod>
</url>
<url>
<loc>/use-cases/</loc>
- <lastmod>2021-07-12T12:19:43-07:00</lastmod>
+ <lastmod>2021-07-12T22:31:35+02: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 90649a5..2f754b7 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02: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 d9e458d..8851aa6 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="336">
diff --git a/use-cases/dish/index.html b/use-cases/dish/index.html
index b2c5f5e..d4a1612 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="249">
diff --git a/use-cases/experity/index.html b/use-cases/experity/index.html
index 5b44c60..245c44f 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="191">
diff --git a/use-cases/onefootball/index.html b/use-cases/onefootball/index.html
index b8e9787..e3831f4 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="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02: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
(“only one person can solve this issue”). 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… 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="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="294">
diff --git a/use-cases/plarium-krasnodar/index.html
b/use-cases/plarium-krasnodar/index.html
index d852547..e4ef1ad 100644
--- a/use-cases/plarium-krasnodar/index.html
+++ b/use-cases/plarium-krasnodar/index.html
@@ -35,12 +35,12 @@
<meta property="og:url" content="/use-cases/plarium-krasnodar/" />
<meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Plarium Krasnodar">
<meta itemprop="description" content="What was the problem? Our Research &
Development department carries out various experiments, and in all of them, we
need to create workflow orchestrations for solving tasks in game dev.
Previously, we didn’t have any suitable tools with a sufficient number of
built-in functions, and we had to orchestrate processes manually and entirely
from scratch every time. This led to difficulties with dependencies and
monitoring when building complex w [...]
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="257">
diff --git a/use-cases/sift/index.html b/use-cases/sift/index.html
index 76dc4d9..733f2a8 100644
--- a/use-cases/sift/index.html
+++ b/use-cases/sift/index.html
@@ -35,12 +35,12 @@
<meta property="og:url" content="/use-cases/sift/" />
<meta property="og:image" content="/images/feature-image.png" />
-<meta property="article:modified_time" content="2021-07-12T12:19:43-07:00"
/><meta property="og:site_name" content="Apache Airflow" />
+<meta property="article:modified_time" content="2021-07-12T22:31:35+02:00"
/><meta property="og:site_name" content="Apache Airflow" />
<meta itemprop="name" content="Sift">
<meta itemprop="description" content="What was the problem? At Sift, we’re
constantly training machine learning models that feed into the core of Sift’s
Digital Trust & Safety platform. The platform gives our customers a way to
discern suspicious online behavior from trustworthy behavior, allowing our
customers to protect their online transactions, maintain the integrity of their
content platforms, and keep their users’ accounts secure. To make this
possible, we’ve built model traini [...]
-<meta itemprop="dateModified" content="2021-07-12T12:19:43-07:00" />
+<meta itemprop="dateModified" content="2021-07-12T22:31:35+02:00" />
<meta itemprop="wordCount" content="641">
