Closed andrewnazarov closed 4 years ago
@andrewnazarov Thanks! I've successfully reproduced this and it's fixed in v0.3.4.
// I've recently changed the default path
from "helmfile.yaml"
to ""
, and this bug was introduced due to some deficiency in the migration logic in the provider to rewrite the state for default values change.
I'm sorry to say that, but Error: Provider produced inconsistent final plan
strikes back (https://github.com/mumoshu/terraform-provider-helmfile/issues/22)
For environments that have no helmfile state changes terraform apply
works and I can confirm it's faster than the intermediate working version was.
For environments that have helmfile state changes terraform apply
fails with the aforementioned Error: Provider produced inconsistent final plan
.
This might be closed, I think
I'm moving forward from the previous version to the most recent and the latest fails for all our environment with
during
terraform plan
stage. There are no changes in any helmfile state except for one. And for that specific environment, the error is the same. Retry didn't help.helmfile version: v0.109.0
Turning debug on I've got the following:
We have concurrency set to 1.