Record removal process in Service Graph Connector for GCP

  • Release version: Washingtondc
  • Updated July 24, 2025
  • 1 minute to read

    • The Service Graph Connector for GCP uses soft deletion and hard deletion to manage the removal of records.

    Record removal is the process of handling data that is no longer needed. For any discovered resources that are deleted later after pulling data, the Service Graph Connector for GCP automatically updates the Install Status field of the associated CMDB CI classes to indicate any retired or deleted records.

    Soft deletion

    Soft deletion involves marking the install status of a record as retired rather than permanently deleting it from the system. The record remains in the database, making it possible to reference or restore it later. Soft deletion for Service Graph Connector for GCP relies on the SG-GCP Extension Attributes [sn_gcp_integ_extension_attributes] table. This table is regularly purged of obsolete records, improving performance and efficiency. The process marks the install status of a record as retired, but the streamlined data structure reduces overhead, enabling quicker processing and better system performance.

    Soft deletion is enabled for the following data sources in Service Graph Connector for GCP:
    • SG-GCP Folder
    • SG-GCP Project
    • SG-GCP Network
    • SG-GCP Subnet
    • SG-GCP Storage Volume
    • SG-GCP Storage Volume Snapshot
    • SG-GCP Security Group
    • SG-GCP VM Instance
    • SG-GCP Load Balancer Pool
    • SG-GCP Load Balancer Pool Member
    • SG-GCP Load Balancer Health Service
    • SG-GCP Load Balancer
    • SG-GCP Load Balancer Service
    • SG-GCP Cloud Database
    • SG-GCP Cloud Function
    • SG-GCP Cloud Object Storage
    • SG-GCP Kubernetes Cluster
    • SG-GCP Kubernetes Node
    • SG-GCP Kubernetes Pod
    • SG-GCP Kubernetes Service
    • SG-GCP Kubernetes Namespace
    • SG-GCP Kubernetes Deployment
    • SG-GCP Kubernetes Replicaset
    • SG-GCP Kubernetes Cluster Roles
    • SG-GCP Kubernetes Cluster Role Binding
    • SG-GCP Kubernetes Node Pool

    Starting with the Service Graph Connector for GCP 1.10 version, the SG-GCP Generic Resource data source uses the post-script method for soft deletion, which relies on the Source [sys_object_source] table. For more information about the post-script method, see Post-script method.

    Hard deletion

    Hard deletion involves permanently deleting a record from the system. The record is removed from the CMDB and can't be referenced or restored later. The SG-GCP Software Inventory data source uses the hard deletion method for the deletion of records.