Rule 3 - Mapping of GCP Resource Types to CMDB CI Classes

Rule Synopsis

These are the rule/s that determine the target CMDB CI Tables/Classes used by CI Sync for each GCP Resource Type.

The target CI Table/CI Class is used by CI Sync for two purposes:

To search for an existing CIs during a CI Update Operation.
To write new CIs during a CI Insert Operation.

Rule Details and Default

The default rule/s are described by the mapping table shown below.

Resource Type	CI Sync Target CI Classes
App Engine Applications	app_engine_applications
Big Query Datasets	cmdb_ci_cloud_database
Cloud SQL Database	cmdb_ci_cloud_database
Cloud Functions	cmdb_ci_web_service
Networks	cmdb_ci_network
Organizations	cmdb_ci_cmp_resource
Projects	cmdb_ci_gcp_project
Redis	cmdb_ci_cloud_database
Regions	cmdb_ci_logical_datacenter
Storage Buckets	cmdb_ci_cloud_storage_account
VM Instances	cmdb_ci_vm_instance

Override Options

Context

Customers may consider changing these mappings to target different CMDB CI Tables/Classes shown above. This can often be required when existing CIs are already present in the CMDB (in Classes different to those shown below) and CI Sync is expected to correlate to the existing CIs.

Options

The target CI Class can be amended per GCP Resource Type.

Overriding via Connection Settings

N/A

Additional Information

N/A

Support Model for Rule Overrides

Question: Can overrides be performed by customers without a Syncfish Extended Implementation and Support Plan?

Answer: No (a plan is needed - see below)

Question: Which Syncfish Extended Implementation and Support Plan is required to obtain overrides of this rule

Answer: Either a Silver Plan or Gold Plan