Deletion of resources/over-write is controlled by Terraform. if the state file is retained and you are applying the new configuration on top (while also having existing config) then the old resources would not go.
if you are using entirely new config and applying it, Terraform being declarative will keep only the resources defined in current template.
e.g. i have a terraform config to deploy VM with 1 disk, network card, and i run this through CPG catalog request - this creates the resources and saves the state file with the resource (VM, 1 disk, network card). now the devops team modifies the terraform config and *adds* 1 more disk to the config. then you can update the catalog item via IaC discovery and change task. with new catalog item, you can choose existing workspace and now it will deploy the config, but it will not remove existing resources as these are already in state file.
btw - you can try the same steps outside of cpg workflow - you will get same result.
Ram
