We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the feature If you import jobs, and then want to link them, I interpret these are the steps:
dbt-jobs-as-code import-jobs --account-id 1111 --project-id 2222 --environment-id 3333 >> jobs_2222_3333.yml
linked_id
jobs: import_1: ... >> jobs: build: ...
dbt-jobs-as-code link jobs_2222_3333.yml
Where I think step 2 and 3 could be done automatically.
import_1
Describe alternatives you've considered Doing this manually
Who will this benefit? People with existing dbt Cloud jobs they want to start managing through dbt-jobs-as-code
Are you interested in contributing this feature? Can do if that helps
The text was updated successfully, but these errors were encountered:
For 2. , you can use the parameter --include-linked-id to add the linked_id.
--include-linked-id
For 3. , what other options would you like?
import_
Sorry, something went wrong.
Ah nice, I missed that, thanks a lot for the explanation! I think based on the job name would make sense!
b-per
No branches or pull requests
Describe the feature
If you import jobs, and then want to link them, I interpret these are the steps:
dbt-jobs-as-code import-jobs --account-id 1111 --project-id 2222 --environment-id 3333 >> jobs_2222_3333.yml
linked_id
to each job with the correct iddbt-jobs-as-code link jobs_2222_3333.yml
Where I think step 2 and 3 could be done automatically.
import_1
Describe alternatives you've considered
Doing this manually
Who will this benefit?
People with existing dbt Cloud jobs they want to start managing through dbt-jobs-as-code
Are you interested in contributing this feature?
Can do if that helps
The text was updated successfully, but these errors were encountered: