Skip to content

Conversation

@kaxil
Copy link

@kaxil kaxil commented Nov 23, 2020

As written in apache#9067, Airflow 2.0 introduces a change that
requires that all Airflow connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections

Preview:
image


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code change, Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in UPDATING.md.

@kaxil kaxil requested a review from ashb November 23, 2020 20:10
@github-actions
Copy link

The PR should be OK to be merged with just subset of tests as it does not modify Core of Airflow. The committers might merge it or can add a label 'full tests needed' and re-run it to run all tests if they see it is needed!

As written in apache#9067,
Airflow 2.0 introduces a change that requires that all Airflow
connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections
@kaxil kaxil force-pushed the show-warning-dup-cons branch from 35aa514 to dd027f1 Compare November 23, 2020 20:13
@kaxil kaxil merged this pull request into v1-10-13 Nov 23, 2020
@kaxil kaxil deleted the show-warning-dup-cons branch November 23, 2020 20:15
kaxil added a commit that referenced this pull request Nov 25, 2020
As written in apache#9067,
Airflow 2.0 introduces a change that requires that all Airflow
connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections
kaxil added a commit that referenced this pull request Dec 10, 2020
As written in apache#9067,
Airflow 2.0 introduces a change that requires that all Airflow
connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections
drdenzy pushed a commit that referenced this pull request Jan 20, 2021
As written in apache#9067,
Airflow 2.0 introduces a change that requires that all Airflow
connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections
kaxil added a commit that referenced this pull request Mar 15, 2021
As written in apache#9067,
Airflow 2.0 introduces a change that requires that all Airflow
connections be unique (whereas Airflow 1.10.x
technically supports two connections with the same name and
potentially the same values).

With this commit, we show "warning" in the Airflow UI for users
with duplicate connections
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants