ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Tunnel to a Compute Engine VM's internal IP with Google Cloud IAP, control access with IAM, and audit sessions in Cloud Logging.
Learn how to run the Cloud SQL Proxy on a Compute Engine VM, authenticate with IAM, and connect to Cloud SQL without managing SSL certificates.
Resolve 403 Forbidden errors when Compute Engine VMs cannot access GCS buckets. Learn to distinguish between IAM permission gaps and restrictive API Access Scopes.
Eliminate SSL certificates and IP whitelists for Cloud SQL by using the Auth Proxy on Compute Engine. A step‑by‑step guide shows how to set up a service account, install the proxy, and connect PostgreSQL locally. Learn the trade‑offs, verify the connection, and secure your database access with IAM.
A CI pipeline needs to retry a SonarQube analysis step when a run fails transiently, and the goal is that a resubmitted report produces exactly one current analysis per build — no duplicated issue counts and no polluted measure history. Two documented approaches exist. Re-running the scanner with the identical sonar.projectKey and sonar.branch.name replaces
A scanner run can complete local analysis yet import no issues because the server rejects the analysis report before it reaches the Compute Engine. The goal is to understand exactly which authorization gate causes that rejection and how it differs from anonymous UI access. The failure occurs on the server-side report submission path behind the Web API, not i
Compute Engine Task Cancellation Behavior The SonarQube Compute Engine (CE) processes analysis reports asynchronously through a worker queue. When a user triggers a cancellation via the API or UI, the system marks the task status as CANCELLED in the database. However, the worker thread may not terminate instantly depending on the current execution phase. Dat
Our SonarQube server intermittently refuses to integrate a scanner report with a Compute Engine error indicating the analysis date is older than the date of the last known analysis for the project (exact wording unverified for our version). The scanner succeeds locally; the failure appears in the project's Background Tasks page during report processing. From
google
gcp
sonarqube