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

Make non-zero exit status default if issues found #313

Merged
merged 1 commit into from Jun 27, 2019
Merged

Conversation

wata727
Copy link
Member

@wata727 wata727 commented Jun 5, 2019

Fixes #243

Many popular linters return a non-zero value as exit status when issues found. On the other hand, TFLint normally always returns zero unless the inspection was not successfully completed.

In my opinion, I believe that the exit status should represent whether the inspection itself is an error or not, but I have understood that it is desirable to return non-zero values by default in some practical situations, such as when running on CI.

Based on the above, this PR changes the default behavior to return non-zero exit status if issues found. It is the same as passing the --error-with-issues option. As a result, the option will be removed in v0.9.0.

Also, in order to keep the prior behavior, we introduce a new --force option. If the option is true, TFLint will return zero as before even if issues found.

@wata727 wata727 merged commit 3faba26 into master Jun 27, 2019
@wata727 wata727 deleted the force_option branch June 27, 2019 13:14
marsam added a commit to marsam/flycheck that referenced this pull request Jul 1, 2019
The --error-with-issues option was removed in v0.9.0. The behavior is
now default. See: terraform-linters/tflint#313
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Feature: enable error-with-issues in .tflint.hcl
1 participant