GCP pattern is executed for each datacenter separately and deletion strategy is triggered
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2023 02:45 AM
If we set up a single service account discovery for GCP for two datacenters, each of the patterns is executed just once. Therefore CIs for both datacenters are included in the single pattern response.
For example we have pattern Google Cloud Platform (GCP) - Cloud SQL DB.
In each datacenter, we have one Cloud Database (Install Status = Installed). Initially we had the deletion strategy set to Retire.
Now here comes the issue. We have Discovery for all Service Accounts and the pattern is triggered twice.
If the pattern is triggered twice for each datacenter, then one of the databases is not found in one pattern and found in the other and vice versa.
With the initial deletion strategy, this would mean that the database would be Retired. With the Keep option, it stays installed, but it's Key Value records (Related entries for the Cloud Database) records are deleted.
So the question is. Does anyone know, how to trigger the pattern just once for each Datacenter (that is the expectation as correct behavior)?
If that is not the expected behavior, is there a way to keep the key values?
I made some unsuccessful attempts to implement the Strategy Script. Maybe that could be an option to restrict the boundaries, similiary to AzureDefaultDeleteStrategy Script..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2024 05:52 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-26-2024 08:50 AM
this issue was fixed in Washington release