Assets that should be there are missing
You may notice that your GCP assets that should be pulled through (e.g. VMs and Cloud DNS assets) are not appearing in the portal.
Why is this happening?
There are a few reasons for this depending on the method of integration used,
If using OAuth for integration:
You may have connected to the wrong Google Account (for example to a personal Google account rather than a work one)
You might have enabled an additional API after initial set up (e.g. added
Compute Engine API
after a time where onlyCloud DNS API
enabled initially or vice versa)
If syncing individual projects:
The Service Account has been created for the wrong GCP Project
The Service Account is missing permissions (missing
Compute Network Viewer
and/orDNS Reader
)The Service account was missing permissions initially and the JSON key was exported before the needed permissions were added
How can I fix it?
Not to worry these issues can be generally be addressed by removing and re-adding your GCP integration.
This will temporarily delete all of your GCP targets but don't worry these will be restored as soon as the integration is re-added.
For OAuth:
Once done, you can then follow these steps in our GCP integration article to re-add your integration.
For syncing individual GCP projects:
There are a few more things to check here compared to using OAuth, but not to worry, the following steps should help get you sorted!
Once done, you can then follow these steps in our GCP integration article to re-add your integration.