Google Cloud

For dashboard setup, choose Continue with Google, authorize a project administrator account, select a project and review the installation. Choose Connect project. Setup and verification continue in the background. Your project is connected after registration completes. Setup uses temporary Google access; ongoing investigation uses a separate read-only identity. You can resume an interrupted setup. If this browser has no saved setup, reopen Google Cloud in the same workspace, sign in as the person who started it and choose Resume setup for the matching project and deployment. After Google reports a failed deployment, choose Review and retry deployment, review the project, existing deployment name and published blueprint release, then choose Retry deployment. This reuses the same request and Google deployment. Authorize Google again if setup access has expired.

To update the service accounts and permissions that Praxen Inc. added to a connected project, open its settings in Praxen Inc. and choose Update in the Project setup row. Authorize Google, review the current and new versions, then choose Update deployment. The update changes the existing deployment, and the project stays connected.

Explore one project's resource types supported by Cloud Asset Inventory, including Compute Engine, Cloud Run, GKE cluster configuration, Cloud SQL, Pub/Sub and Storage. Resource logs and metrics currently cover Pub/Sub topics and Storage buckets.

Registration can complete before initial inventory finishes. If this browser restores a script-based request, run its saved setup script and choose Verify and connect after it finishes. Pending requests last seven days. Disconnect in Praxen Inc., then destroy the Google deployment or Terraform module to remove its resources. Kubernetes API access, organization-wide discovery and automated Google changes are outside this connection's scope.

Inventory freshness

Cloud Asset Inventory is eventually consistent and can miss updates. Some resource types synchronize hours apart, so Praxen Inc.'s 15-minute reconciliation does not guarantee 15-minute source freshness. Broad resource deletions use asset deletion events. For resources missing from a current snapshot, Praxen Inc. also checks Google's resource history within its 35-day retention to confirm deletion. Unknown, expired or ambiguous history retains the resource until further evidence or cleanup. Pub/Sub topics and Storage buckets also reconcile direct API not-found responses. Inventory events update the graph; log investigations query Google directly. See Google's consistency and resource freshness guidance.