Git sync doesn't clone repo on right location
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- git, kubernetes, rust
- Domain
- devops, infrastructure
Research direction
Start from the deployment file's dagsGitSync configuration and trace how the gitFolder value is handled during repository cloning. Reproduce the configuration with gitFolder: ./dags and verify that the repository is placed at the configured location; done means the clone path matches that value.
Written by the indexing model from the issue text.
Description
Affected Stackable version
24.7.0
Affected Apache Airflow version
nightly
Current and expected behavior
Gitsync clone the repo but not on expected location specified in gitFolder defined in deployment file.
dagsGitSync:
- repo: https://git_url/airflow-dags.git
branch: release/test
gitFolder: ./dags
credentialsSecret: git-credentials
Possible solution
No response
Additional context
No response
Environment
No response
Would you like to work on fixing this bug?
None
- Dominant language
- Rust
- Stars
- 32
- Forks
- 6
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stackabletech/airflow-operator
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
stackabletech/airflow-operator#898 ·
Maintainers usually reply within 1 day
-
good first issue type/feature-improvement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
stackabletech/airflow-operator#760 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 42/100
stackabletech/airflow-operator#697 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/airflow-operator#638 ·
Maintainers usually reply within 1 day
-
type/feature-new
Difficulty 5/5 Over a week Newbie friendliness 25/100
stackabletech/airflow-operator#593 ·
Maintainers usually reply within 1 day
All issues in stackabletech/airflow-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
2 advisory ignore entries no longer match anything (`bytes`, `time` already patched in `Cargo.lock`)Possibly taken @zyl71 claimed this today. Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
stackabletech/druid-operator#905 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day