Skip to content

Feat #976: Add skip_plan_validation attribute for CRD bootstrapping scenarios - #1855

Open
dennismdejong wants to merge 1 commit into
hashicorp:mainfrom
dennismdejong:feat/976-crd-bootstrap
Open

Feat #976: Add skip_plan_validation attribute for CRD bootstrapping scenarios#1855
dennismdejong wants to merge 1 commit into
hashicorp:mainfrom
dennismdejong:feat/976-crd-bootstrap

Conversation

@dennismdejong

@dennismdejong dennismdejong commented Jul 27, 2026

Copy link
Copy Markdown

When a Helm chart and its required CRDs are deployed in the same Terraform run, the provider fails during plan because it tries to validate rendered manifests against the Kubernetes API before the CRDs exist.

This adds a new skip_plan_validation boolean attribute (default: false) to helm_release. When set to true, the plan-time dry-run (which validates rendered manifests against the Kubernetes API) is skipped, allowing CRDs and their custom resources to be deployed in the same Terraform run.

Closes #976

@dennismdejong
dennismdejong requested review from a team, iam404 and rigalGit as code owners July 27, 2026 20:00
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.

Applying CRD and chart on same TF

1 participant