Automic VaultAutomic Vault

brew

cloud-sql-proxy mit Homebrew, scoop installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für cloud-sql-proxy in AI-Agent-Workflows.

InstallationsbefehlSicherheitshinweise

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install cloud-sql-proxy

local Homebrew formula metadata

Windows

Scoopverifiziert · 92%
scoop install main/cloud-sql-proxy

Scoop official bucket manifest trees · bucket/cloud-sql-proxy.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Utility for connecting securely to your Cloud SQL instances

Befehle und Aliase

  • cloud-sql-proxy

Verlauf

Projektgeschichte und Nutzung

Cloud SQL Auth Proxy is Google's CLI for making secure local or sidecar connections to Cloud SQL instances. It is historically important because it packages Google Cloud database connectivity, IAM authorization, and TLS handling into a standalone executable used across local development, VMs, containers, and Kubernetes-style deployments.

Projektgeschichte

The GoogleCloudPlatform/cloud-sql-proxy repository was created in 2015 and remains the official upstream for the Cloud SQL Auth Proxy. The README describes it as a utility for secure Cloud SQL connections with IAM authorization and TLS 1.3 encryption, avoiding manual certificate management.

The v2 migration guide documents a major CLI evolution from the old `cloud_sql_proxy` executable to `cloud-sql-proxy`, with more explicit flags, environment-variable support, a new container image name, and changed connection behavior.

Adoptionsgeschichte

Official docs distribute platform-specific binaries through Google storage, document `go install`, and point to GitHub releases. The input package-manager facts show Homebrew and Scoop packaging, reflecting common workstation installation patterns.

The README positions language-specific Cloud SQL connectors for Go, Java, Python, and Node.js as alternatives when users prefer in-process connectivity, so the proxy sits beside a broader connector ecosystem rather than replacing it.

Wie es verwendet wird

Users run the proxy with one or more Cloud SQL instance connection names, optionally choosing TCP ports, Unix sockets, private IP behavior, IAM database authentication, metrics, health checks, service-account impersonation, or a credentials-file flag.

The proxy obtains credentials through Google Application Default Credentials by default, and can also take an OAuth token or service-account key file path supplied by the user.

Warum Paket-Nerds sich dafür interessieren

For package nerds, Cloud SQL Auth Proxy is a classic cloud vendor CLI where binary naming, major-version migration, install channel, and authentication defaults all matter. The v1-to-v2 executable rename is exactly the sort of detail package formulas and scripts must track.

It is also significant because the same package has to serve developer laptops, CI jobs, VM agents, and container images while remaining aligned with Google Cloud IAM and Cloud SQL behavior.

Zeitleiste

  • 2015: GoogleCloudPlatform/cloud-sql-proxy GitHub repository metadata was created.
  • v2: Migration guide documents the rename from cloud_sql_proxy to cloud-sql-proxy and the new container image name.
  • v2.17.1: README records signed Windows binaries starting with this version.

Related projects

  • Cloud SQL Go, Java, Python, and Node.js connectors are official related projects named by the README.
  • Google Cloud SDK and Application Default Credentials provide the usual authentication environment.
  • The older v1 Cloud SQL proxy behavior is documented through the upstream migration guide.

Sicherheitslage

Risikostufe: orange

broad file, network, media, or database tool signal. infrastructure mutation or orchestration signal.

Risikoklassifikator

orange Risiko · mittel Konfidenz · infrastructure

Warum

  • broad file, network, media, or database tool signal
  • infrastructure mutation or orchestration signal

Signale

  • text:cloud
  • text:sql

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
cloud-sql-proxycliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version2.23.0
Manager aktualisiert2026-06-26
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv2.23.0

https://github.com/GoogleCloudPlatform/cloud-sql-proxy

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:cloud-sql-proxy
Version2.23.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/cloud-sql-proxy
Homepagehttps://github.com/GoogleCloudPlatform/cloud-sql-proxy
Repositoryhttps://github.com/GoogleCloudPlatform/cloud-sql-proxy
Upstream-Dokumentationhttps://docs.cloud.google.com/sql/docs/postgres/sql-proxy
LizenzApache-2.0
Quellarchivhttps://github.com/GoogleCloudPlatform/cloud-sql-proxy/archive/refs/tags/v2.23.0.tar.gz
Zuletzt aktualisiert2026-06-26T15:03:55Z
Pulseupdated
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecloud-sql-proxy
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Scoop95%

main/cloud-sql-proxy

scoop install main/cloud-sql-proxy
  • normalized package name match
  • Abgeglichen nach: Cloud Sql Proxy
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/cloud-sql-proxy.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Paketgraph

Links stammen aus dem lokalen Paketbeziehungsgraph, Ergänzungen, Abhängigkeitskanten, Ecosystem-Matches und Paket-Hub-Mitgliedschaft.

Verwandte Tools

  • goBuild dependency declared by Homebrew.

Gleicher Workflow

  • pscaleShares av.db curated category or tags: cli, cloud-infrastructure, database.
  • gcsfuseShares av.db curated category or tags: cli, cloud-infrastructure, google-cloud.
  • terracognitaShares av.db curated category or tags: cli, cloud-infrastructure, google-cloud.
  • actions-batchShares av.db curated category or tags: cli, cloud-infrastructure.
  • aiacShares av.db curated category or tags: cli, cloud-infrastructure.
  • aiven-clientShares av.db curated category or tags: cli, cloud-infrastructure, database.

Agent-Sicherheitsleitfäden

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment