Open mpresling opened 1 month ago
Has anyone else seen or heard of this issue? Could it just be the way I'm using it? Any ideas?
Note: argomark == mpresling 😀
Running into this too. Seems like there is no way to use ec_deployment_traffic_filter
via terraform.
Between this and the lack of support for customer-managed keys via this provider, I'm having trouble coming up with any sensible workflow for working with elastic from code.
Readiness Checklist
Expected Behavior
Creating a new Traffic Filter with ec_deployment_traffic_filter completes successfully.
Current Behavior
After creating the resource in my account in EC (which happens successfully and it's visible in the console) the provider is unable to read back the resource details/id to store the state.
I also cannot import an existing resource (note: portion of ID replaced with xxx):
Terraform definition
Simple IP filter:
Azure Private Link filter:
Steps to Reproduce
Note: other changes such as
ec_deployment
complete successfully prior to the traffic filters failing.Context
This used to work and I was able to build the lower environments fine. Then after EC 8.15.0 was released this started failing and I can no longer manage the deployment fully via Terraform.
After upgrading to elastic/ec 0.11.0 it resolved some other problems with
clusters.cluster_settings_change_prohibited: The requested cluster metadata changes are not permitted
, but not this one.Your Environment