This is a change discussed long time back in https://github.com/apache/airflow/pull/3889#issuecomment-507635839
Essentially, the 7 permission-resource pairs are added for all users:
- can_this_form_post on UserInfoEditView
- can_this_form_get on UserInfoEditView
- can_userinfo on UserDBModelView
- userinfoedit on UserDBModelView
- can_this_form_post on ResetMyPasswordView
- can_this_form_get on ResetMyPasswordView
- resetmypassword on UserDBModelView
In addition, can_userinfo is added for all possible User ModelViews, so users can also view profile when
the webserver is using different setting-ups.
But they are ONLY allowed to edit profile and reset password when it's UserDBModelView
This is based heavily on the UPGRADING_to_2.0.md file. The intent here is
to make user facing and available as part of the Airflow documentation.
This is still a work in progress.
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
Co-authored-by: Daniel Imberman <daniel.imberman@gmail.com>
Co-authored-by: Ash Berlin-Taylor <ash_github@firemirror.com>
When building the docs locally (not docker, cos I'm on linux and a
grouch at times 😁) I appear to be using a different backend to
enchant to check spelling, and it noticed these two issues
- spelling of yandex in extra-packages unrecognized
- a smart quote instead of a backtick breaking a link
* Apply labels to Docker images in a single instruction
While looking at the build logs for something else I noticed this
oddity at the end of the CI logs:
```
Tue, 08 Dec 2020 21:20:19 GMT Step 125/135 : LABEL org.apache.airflow.distro="debian"
...
Tue, 08 Dec 2020 21:21:14 GMT Step 133/135 : LABEL org.apache.airflow.commitSha=${COMMIT_SHA}
Tue, 08 Dec 2020 21:21:14 GMT ---> Running in 1241a5f6cdb7
Tue, 08 Dec 2020 21:21:21 GMT Removing intermediate container 1241a5f6cdb7
```
Applying all the labels took 1m2s! Hopefully applying these in a single
layer/command should speed things up.
A less extreme example still took 43s
```
Tue, 08 Dec 2020 20:44:40 GMT Step 125/135 : LABEL org.apache.airflow.distro="debian"
...
Tue, 08 Dec 2020 20:45:18 GMT Step 133/135 : LABEL org.apache.airflow.commitSha=${COMMIT_SHA}
Tue, 08 Dec 2020 20:45:18 GMT ---> Running in dc601207dbcb
Tue, 08 Dec 2020 20:45:23 GMT Removing intermediate container dc601207dbcb
Tue, 08 Dec 2020 20:45:23 GMT ---> 5aae5dd0f702
```
* Update Dockerfile
As discussed in AIP-21
* Rename airflow.sensors.external_task_sensor to airflow.sensors.external_task
* Rename airflow.sensors.sql_sensor to airflow.sensors.sql
* Rename airflow.contrib.sensors.weekday_sensor to airflow.sensors.weekday
In 2.0 and master branch, there are permission & view name changes for DAG-level access control.
- Permission: "can_dag_read"/"can_dag_edit" -> "can_read"/"can_edit"
- View: "all_dags" -> "DAGs"
These were missed to be reflected in the doc, and this PR addresses it.
We already have 80 minutes timeout for Postgres and MySQL tests.
Currently some of Sqlite tests on PRs are timing out since they
are taking more than 60 mintues.
Example: https://github.com/apache/airflow/runs/1518719040
As discussed in AIP-21
* Rename airflow.hooks.base_hook to airflow.hooks.base
* Rename airflow.hooks.dbapi_hook to airflow.hooks.dbapi
* Rename airflow.sensors.base_sensor_operator to airflow.sensors.base
* Rename airflow.sensors.date_time_sensor to airflow.sensors.date_time
* Rename airflow.sensors.time_delta_sensor to airflow.sensors.time_delta
Co-authored-by: Kaxil Naik <kaxilnaik@apache.org>
* The 4 providers (http, ftp, sqlite, imap) are popular
and they do not require any additionl dependencies so we decided
to include them by default in Airflow 2.0
Co-authored-by: Jarek Potiuk <jarek.potiuk@polidea.com>
* Update setup.py
Co-authored-by: Jarek Potiuk <jarek.potiuk@polidea.com>
Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Connection form behaviour depends on the connection type. Since we've
separated providers into separate packages, the connection form should
be extendable by each provider. This PR implements both:
* extra fields added by provider
* configurable behaviour per provider
This PR will be followed by separate documentation on how to write your
provider.
Also this change triggers (in tests only) the snowflake annoyance
described in #12881 so we had to xfail presto test where monkeypatching
of snowflake causes the test to fail.
Part of #11429
Updates comments in setup.py according to the latest 2.0 agreements
about semver and clarifies use for arrays defined in setup.py.
We will refactor those after 2.0 further, but for now we keep
the current structure.
This build combines building both CI and PROD image in one
script execution on DockerHub per python version.
First the CI image is build and secondly, the image is used
to build all the packages from sources and then those
packages are used to build the PROD image.
Resulting image will be package image built from latest sources.
Closes: #12261