Skip to content

terraform/lint/minimum-failure-severity

Cluster UUID that created the alert

Overview

This parameter controls the --minimum-failure-severity flag passed to TFLint during Terraform plan validation. It determines which severity levels cause the terraform-apply task to fail.

Severity Levels (in order of increasing severity)

  • notice - Informational messages (lowest severity, rarely causes issues)
  • warning - Potential problems that may or may not be issues
  • error - Definite problems that should be fixed (highest severity)

Common Use Cases

Default: Fail on Warnings (Strict)

terraform/lint/minimum-failure-severity: "warning"
- Fails on both warnings and errors - Most strict validation - Default behavior (backward compatible)

terraform/lint/minimum-failure-severity: "error"
- Shows warnings but doesn't stop provisioning - Useful for providers with unavoidable warnings (e.g., vSphere PXE unused variables) - Recommended for production use

Debug: Never Fail on Lint Issues

terraform/lint-templates: []
- Disables linting entirely - Fastest option but skips validation - Use only for troubleshooting

Example: vSphere PXE Provisioning

vSphere PXE mode generates unused Terraform variables (drp_public_key, drp_names, etc.) that trigger warnings. These are harmless - the variables exist for compatibility with other cloud providers but aren't referenced in vSphere templates.

Solution: 

# Set on the resource broker to allow warnings
drpcli resource_brokers set vsphere-broker \
  param terraform/lint/minimum-failure-severity to "error"

TFLint Exit Codes

  • Exit 0: No issues found (or all below minimum severity)
  • Exit 2: Issues found at or above minimum severity
  • Exit 1: TFLint execution error (syntax error, config issue, etc.)