- All authentication backends in `airflow/contrib/auth`
are base on the `user` model which has already been
removed earlier (https://github.com/apache/airflow/pull/4577#issuecomment-607202089)
- Security related documentation is out-dated,
especially the LDAP and OAuth integration sections.
It still directs user to the configuration of "old" web UI
which has already been removed in master branch.
nvd3 has a dependency on python-slugify which pulls in a
GPL dependency by default, which we don't want.
This commit brings in nvd3 0.15.0 and slugify 2.0.1 WITH NO CHANGES -
those will come in the next commit
JIRA:
https://issues.apache.org/jira/browse/AIRFLOW-1291
* Update NOTICE with proper year range for ASF
copyright
* Break down LICENSE into
licenses/LICENSE-[project].txt
* add license header to jqClock.min.js
[AIRFLOW-1291] Update NOTICE and LICENSE files to
match ASF requirements
* Update NOTICE with proper year range for ASF
copyright
* Break down LICENSE into
licenses/LICENSE-[project].txt
* add license header to jqClock.min.js
fix license check
Closes#2354 from
mistercrunch/copyright_license_touchups
This implements a framework for API calls to Airflow. Currently
all access is done by cli or web ui. Especially in the context
of the cli this raises security concerns which can be alleviated
with a secured API call over the wire.
Secondly integration with other systems is a bit harder if you have
to call a cli. For public facing endpoints JSON is used.
As an example the trigger_dag functionality is now made into a
API call.
Backwards compat is retained by switching to a LocalClient.