Skip to content

Conversation

@drdenzy
Copy link
Contributor

@drdenzy drdenzy commented May 19, 2021

Mounting DAGs from a private Github repo using Git-Sync sidecar is
quite complex because of the several steps required and the many
other moving parts.

The PR aims to ameliorate some of these pain points so that users can
have a smoother experience when mounting their DAGs from private repos
on Github.


^ 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.

Mounting DAGs from a private Github repo using Git-Sync sidecar is
quite complex because of the several steps required and the many
other moving parts.

The PR aims to ameliorate some of these pain points so that users can
have a smoother experience when mounting their DAGs from private repos
on Github.
Copy link
Member

@potiuk potiuk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Love it. I think it's very much needed.

But I think you need to fix the license indentation :)

@github-actions github-actions bot added the okay to merge It's ok to merge this PR as it does not require more tests label May 19, 2021
@github-actions
Copy link

The PR is likely ready to be merged. No tests are needed as no important environment files, nor python files were modified by it. However, committers might decide that full test matrix is needed and add the 'full tests needed' label. Then you should rebase it to the latest master or amend the last commit of the PR, and push it with --force-with-lease.

@drdenzy
Copy link
Contributor Author

drdenzy commented May 19, 2021

Love it. I think it's very much needed.

But I think you need to fix the license indentation :)

Oh yeah! Thanks, Jarek.

.. code-block:: bash
helm install airflow --namespace <your-airflow-namespace> . -f override-values.yaml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This would likely change when the chart is released?.

Supposing the user added the released chart to helm with:
helm repo add apache-airflow-chart path/to/chart.

The install should be:
helm install airflow --namespace <your-airflow-namespace> apache-airflow-chart/airflow -f override-values.yaml

I don't know the best way to add it to this doc, maybe we should merge this and update the doc when the Chart is released? @kaxil

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, yes.

I will create a PR while releasing the chart to make sure we are consistent everywhere in the Helm Chart docs.

Copy link
Member

@kaxil kaxil left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well done @Dr-Denzy 👏 -- As a follow up to this we could generalize this to any "private git repo" and the point raised by @ephraimbuddy which I will cover as part of releasing Helm Chart.

@kaxil kaxil merged commit e1cdad0 into apache:master May 19, 2021
@kaxil kaxil deleted the helm-chart-git-sync-ssh-doc branch May 19, 2021 13:23
@kaxil kaxil added the area:helm-chart Airflow Helm Chart label May 19, 2021
@kaxil kaxil added this to the Airflow Helm Chart 1.1.0 milestone Jul 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:helm-chart Airflow Helm Chart kind:documentation okay to merge It's ok to merge this PR as it does not require more tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants