New issue
Advanced search Search tips

Issue 868581 link

Starred by 2 users
Status: Available
Owner: ----
Cc:
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature



Sign in to add a comment

CLI tools that access CIDB should automatically use Cloud SQL Proxy

Project Member Reported by la...@chromium.org, Jul 27 
Rather than whitelisting corp IPs we should use https://cloud.google.com/sql/docs/mysql/sql-proxy which uses user-based authentication instead.

While we do intend to move away from direct CIDB access I think realistically these tools won't have replacements in the medium term.

Comment 1 by la...@chromium.org, Jul 31 

Context: crbug.com/868197

Comment 2 by dgarr...@chromium.org, Aug 2 

Alternatively, they could use a CI web API and not use SQL at all.

Comment 3 by la...@chromium.org, Aug 15

Status: Available (was: Untriaged)

Comment 4 by athilenius@chromium.org, Aug 21 

Trying to understand a bit more: This was done recently for Chromite wasn't it? And by Cloud SQL Proxy you mean using a service account which goes through a proxy for the actual MySQL connection?

Comment 5 by la...@chromium.org, Aug 21 

> This was done recently for Chromite wasn't it?

Not that I'm aware of. lib/cidb.py doesn't reference a proxy anywhere anyway...
►

Sign in to add a comment