Datadog Terraform Provider Version
v3.57.0
Terraform Version
v1.12.2
What resources or data sources are affected?
datadog_software_catalog
Terraform Configuration Files
Relevant debug or panic output
no entity is found in the response,
path=/api/vZ/catalog/entity?include=raw_schema&filter[ref]=xxxxxx
response={"data": [], "meta" : {"count":0, "includeCount":0}, "links":{"self":"/api/v2/catalog/entity?filter%5Bref%5D=xxxxxx\u0026include=raw_schema\u0026page%5B1imit%5D=100\u0026page%5Boffset%5D=0"}}
Expected Behavior
Terraform is able to gracefully handle that the resource has been deleted and suggest creating it again.
Actual Behavior
Provider blows up with no entity is found in the response error.
The datadog provider MUST gracefully handle resources being deleted outside of Terraform.
Steps to Reproduce
- Create a
datadog_software_catalog resource
- Run
terraform apply
- Delete the created catalogue entry from within the DataDog UI
- Run
terraform apply again
Important Factoids
There appears to be code within the provider to handle a 404 response gracefully, but according to the corresponding docs a 404 response is not possible.
References
No response
Datadog Terraform Provider Version
v3.57.0
Terraform Version
v1.12.2
What resources or data sources are affected?
datadog_software_catalogTerraform Configuration Files
Relevant debug or panic output
Expected Behavior
Terraform is able to gracefully handle that the resource has been deleted and suggest creating it again.
Actual Behavior
Provider blows up with
no entity is found in the responseerror.The datadog provider MUST gracefully handle resources being deleted outside of Terraform.
Steps to Reproduce
datadog_software_catalogresourceterraform applyterraform applyagainImportant Factoids
There appears to be code within the provider to handle a 404 response gracefully, but according to the corresponding docs a 404 response is not possible.
References
No response