Skip to content
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

Change dbt list command to always return 0 as exit code #2892

Merged
merged 2 commits into from
Nov 17, 2020
Merged

Change dbt list command to always return 0 as exit code #2892

merged 2 commits into from
Nov 17, 2020

Conversation

rsella
Copy link
Contributor

@rsella rsella commented Nov 17, 2020

resolves #2886

Description

Change 'dbt list' command to always return 0 as exit code

First PR, any comment is greatly appreciated

Checklist

  • I have signed the CLA
  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt next" section.

@cla-bot cla-bot bot added the cla:yes label Nov 17, 2020
Copy link
Contributor

@jtcohen6 jtcohen6 left a comment

Choose a reason for hiding this comment

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

This is looking good! Thanks for the contribution @rsella

Looking at the integration test failures, there are a few more tests to switch expect_pass, namely in 062_defer_state_test.

CHANGELOG.md Outdated
@@ -11,6 +11,7 @@
- Fix Redshift adapter `get_columns_in_relation` macro to push schema filter down to the `svv_external_columns` view ([#2855](https://github.com/fishtown-analytics/dbt/issues/2854))
- Add `unixodbc-dev` package to testing docker image ([#2859](https://github.com/fishtown-analytics/dbt/pull/2859))
- Increased the supported relation name length in postgres from 29 to 51 ([#2850](https://github.com/fishtown-analytics/dbt/pull/2850))
- dbt list command always return 0 as exit code ([#2866](https://github.com/fishtown-analytics/dbt/issues/2886))
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- dbt list command always return 0 as exit code ([#2866](https://github.com/fishtown-analytics/dbt/issues/2886))
- dbt list command always return 0 as exit code ([#2886](https://github.com/fishtown-analytics/dbt/issues/2886), [#2892](https://github.com/fishtown-analytics/dbt/issues/2892))

Could you also add yourself to the list of Contributors below?

@jtcohen6 jtcohen6 merged commit ec0f3d2 into dbt-labs:dev/kiyoshi-kuromiya Nov 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

dbt ls should return a zero exit code when no models are selected
2 participants