Error when running dlt deploy cli with airflow-composer parameter
- Dominant language
- Python
- Stars
- 5.9k
- Forks
- 600
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 38
Description
### dlt version
1.4.1
### Describe the problem
Hello,
I am encountering an issue when trying to deploy a pipeline on Airflow-Composer.
The pipeline works perfectly, but when I run the command :
`dlt deploy .\rest_api_pipeline.py airflow-composer`
I get the following error:
```
Your current repository origin is not set to GitHub but to [https://gitlab.*****/test-dlt-composter.git](https://gitlab.%2A%2A%2A%2A%2A/test-dlt-composter.git).
You must change it to be able to run the pipelines with GitHub Actions: https://docs.github.com/en/get-started/getting-started-with-git/managing-remote-repositories
NOTE: Please refer to our docs at 'https://dlthub.com/docs/walkthroughs/deploy-a-pipeline' for further assistance.
```
I do not understand why the CLI is trying to use GitHub Actions, as I haven’t specified anything in my configuration.
I therefore believe this might be a bug.
### Expected behavior
Generation of a DAG file with my pipeline
### Steps to reproduce
Install latest version of dlt
create a simple rest api to bigquery pipeline
run pipeline to check that all is working fine
run `dlt deploy .\rest_api_pipeline.py airflow-composer` command
### Operating system
Windows
### Runtime environment
Local
### Python version
3.9
### dlt data source
service now rest api
### dlt destination
Google BigQuery
### Other deployment details
_No response_
### Additional information
_No response_
Contributor guide
Research direction
Start by tracing the `dlt deploy .\rest_api_pipeline.py airflow-composer` command and the deployment path that checks the repository origin. Reproduce the error with the Airflow-Composer target, then verify that a valid GitLab-origin repository can generate the expected DAG without incorrectly requiring GitHub Actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, git, github-actions, python
- Domain
- cli, cloud, data-engineering
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100