-
Notifications
You must be signed in to change notification settings - Fork 14.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[AIRFLOW-6462] Limit exported variables in Dockerfile/Breeze #7057
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mik-laj
commented
Jan 5, 2020
@@ -266,8 +271,6 @@ ENV AIRFLOW_REPO=${AIRFLOW_REPO} | |||
ARG AIRFLOW_BRANCH=master | |||
ENV AIRFLOW_BRANCH=${AIRFLOW_BRANCH} | |||
|
|||
ENV AIRFLOW_GITHUB_DOWNLOAD=https://raw.githubusercontent.com/${AIRFLOW_REPO}/${AIRFLOW_BRANCH} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is an unused variable.
kaxil
approved these changes
Jan 5, 2020
potiuk
approved these changes
Jan 5, 2020
Needs rebase :) |
mik-laj
changed the title
[AIRFLOW-6462][depends on AIRFLOW-6461] Limit exported variables in Dockerfile/Breeze
[AIRFLOW-6462] Limit exported variables in Dockerfile/Breeze
Jan 5, 2020
I rebased and added a small fixup related to Apache RAT and Hadoop/Hive. |
potiuk
approved these changes
Jan 5, 2020
potiuk
pushed a commit
that referenced
this pull request
Jan 21, 2020
(cherry picked from commit 5ae2f96)
kaxil
pushed a commit
that referenced
this pull request
Jan 22, 2020
(cherry picked from commit 5ae2f96)
kaxil
pushed a commit
that referenced
this pull request
Jan 23, 2020
(cherry picked from commit 5ae2f96)
potiuk
pushed a commit
that referenced
this pull request
Jan 26, 2020
(cherry picked from commit 5ae2f96)
kaxil
pushed a commit
that referenced
this pull request
Jan 26, 2020
(cherry picked from commit 5ae2f96)
galuszkak
pushed a commit
to FlyrInc/apache-airflow
that referenced
this pull request
Mar 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a lot of variables after typing the command
export
in a clean environment. I would like to limit their number. to make the result of the export command more readable.After:
Before:
Link to JIRA issue: https://issues.apache.org/jira/browse/AIRFLOW-6462
[AIRFLOW-NNNN]
, where AIRFLOW-NNNN = JIRA ID*(*) For document-only changes, no JIRA issue is needed. Commit message starts
[AIRFLOW-XXXX]
.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.
Read the Pull Request Guidelines for more information.