You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
stackit_cdn_distribution: empty WAF rule group lists cause "Provider produced inconsistent result after apply" #1629
Error: Provider produced inconsistent result after apply
When applying changes to
module.cdn_distribution["website"].stackit_cdn_distribution.this,
provider "registry.terraform.io/stackitcloud/stackit"
produced an unexpected new value:
.config.waf.enabled_rule_group_ids:
length changed from 0 to 1.
This is a bug in the provider, which should be reported in the provider's own issue tracker.
Expected behavior
The provider should accept explicitly configured empty lists for the WAF rule group attributes and complete the apply successfully.
No provider state inconsistency should occur when these attributes are configured as empty collections..
Environment
OS: Windows
Terraform version (see terraform --version): v1.15.8
Version of the STACKIT Terraform provider: v0.104.0
Additional information
The issue only occurs when the attributes are explicitly configured as empty lists.
If the attributes are omitted completely, terraform apply succeeds without errors.
This behavior suggests that the provider does not correctly handle empty collections returned from the API, resulting in an inconsistent Terraform state after apply.
Hey @Met1nG, thanks for raising this issue. I was able to reproduce it and i think it might be API related. I've informed the responsible team and will keep you updated.
Hello @Met1nG, the issue was fixed in the Backend/API by the service team. So you don't need a new Terraform version to have the fix. If the issue persists, feel free to reopen the issue!
Best regards,
Jonas Schlecht from the STACKIT Developer Tools team
Activity
SerseusWasTaken commentedon Jul 31, 2026
Hey @Met1nG, thanks for raising this issue. I was able to reproduce it and i think it might be API related. I've informed the responsible team and will keep you updated.
SerseusWasTaken commentedon Oct 29, 2026
Hello @Met1nG, the issue was fixed in the Backend/API by the service team. So you don't need a new Terraform version to have the fix. If the issue persists, feel free to reopen the issue!
Best regards,
Jonas Schlecht from the STACKIT Developer Tools team