search

claranet / terraform-provider-zabbix

Terraform provider for Zabbix.
MIT License
28 stars 18 forks source link

Unable to destroy host #34

Open syphernl opened 2 years ago

syphernl commented 2 years ago

When destroying using terraform plan -destroy -out destroy.plan we're getting an error:

│ Error: -32602 (Invalid params.): Invalid parameter "/1": a number is expected.

The only way to be able to fully destroy an infra-stack is by removing the Zabbix Host manually via the Zabbix Webinterface and from the state using:

terraform state rm zabbix_host.this
pdecat commented 2 years ago

What version of terraform, the provider and Zabbix server are in use?

Does this error happen with just terraform destroy?

Does you have a minimum configuration sample to reproduce this issue?

mahsoud commented 2 years ago

We are seeing this with latest version of provider and zabbix v6

scytem commented 2 years ago

@pdecat please check the PR above. Seems like it's working after this fix.

scytem commented 2 years ago

@pdecat do you plan to bump the provider version to implement this fix?

scytem commented 1 year ago

@pdecat Hello! Seems like you improving tests. Is there any news related to this fix? I'm using my own downstream fork build, but probably I can help somehow.

aloisiobilck commented 1 year ago

Hi, Any news? I am using zabbix 6, terraform 1.3.x and the latest version 0.4.0

rdavisunr commented 1 year ago

Also looking for news on this one. When will the release be available?

pdecat commented 1 year ago

@pdecat Hello! Seems like you improving tests. Is there any news related to this fix? I'm using my own downstream fork build, but probably I can help somehow.

Hi @scytem, sorry for the silence here.

When all the compatibility issues with newer Zabbix server versions started being reported, I indeed spent some time testing the provider across several versions of Zabbix server, only to discover maintaining compatibility with all those versions would mean a lot of work in both the API lib and the provider.

I'm starting to believe the best way forward would be have compatibility with a single Zabbix server major version in each provider version. A bit like Gitlab did recently. Still a lot of work to follow server API changes across versions, though.

Anyway, I do not have the bandwidth to work on this right now.