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
Hello,
Reporting the following customer error as recommended in the obtained message.
The error occurred when trying to define the deployment specifying a snapshot repository; it seems like there’s an issue with the management of snapshot repository configuration.
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.elasticsearch["xxx-qa-nonprod"].ec_deployment.xxx-qa-nonprod, provider "provider[\"registry.terraform.io/elastic/ec\"]" produced an unexpected new value: .elasticsearch.snapshot.repository: was cty.ObjectVal(map[string]cty.Value{"reference":cty.UnknownVal(cty.Object(map[string]cty.Type{"repository_name":cty.String}))}), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
Terraform v1.8.2.
Terraform-provider-ec v.0.10.0.
Elastic Cloud v8.13.3.
The text was updated successfully, but these errors were encountered:
I have also encountered this error message while trying to create a custom snapshot repository and associate it with a cluster created via ec_deployment (although this feels a bit chicken and egg at the moment unless there's some checks that aren't performed)
To add, I upgraded to 0.12.1 and added an ignore_lifecycle on the ec_deployment to see if it was just a configuration issue. Unfortunately, replanning the module makes it believe it needs to be updated again. I also ran a manual snapshot and it was not added to the custom repository which makes me believe the change isn't persisting.
Hello,
Reporting the following customer error as recommended in the obtained message.
The error occurred when trying to define the deployment specifying a snapshot repository; it seems like there’s an issue with the management of snapshot repository configuration.
The text was updated successfully, but these errors were encountered: