Qualys Agent Messes with Terraform state

Occasional Visitor

The Azure subscription I'm working on has defender for cloud enabled. All our resources are managed by terraform but what seems to happen is that our virtual machines might end up with the Qualys agent attached to them. This means that running terraform destroy does not destroy the Qualys agent and will end up with terraform hanging either on the create or delete. Is there any way to include the agent into Terraform state or prevent the agent from being attached to a vm?

Alternatively if the agent would not prevent vm deletion or creation that could work too. 

 

 

0 Replies