Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Option to suppress auth warning when using install_components without authentication

Offen
#731 1 Kommentar 2 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
38/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Veraltet
Tech-Stack
github-actions, google-cloud, typescript
Bereich
ci-cd, cloud, devops

Rechercherichtung

Start by locating the action's input definitions and the code that emits the unauthenticated warning, then inspect how install_components and project_id are handled. Compare the proposed skip_auth_check input with the automatic-skip alternative; done means component-only workflows can avoid the misleading warning while authentication warnings remain for relevant configurations.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

TL;DR

When using setup-gcloud solely to install components (e.g., cloud-firestore-emulator for testing), the action emits a warning:

The gcloud CLI is not authenticated (or it is not installed). Authenticate by adding the "google-github-actions/auth" step prior this one.

This warning is misleading for users who intentionally don't need authentication — they only need gcloud to install a component. There should be a way to suppress it.

Use Case

We use setup-gcloud in CI to install the Firestore emulator for integration tests:

- name: Set up Google Cloud SDK
  uses: google-github-actions/setup-gcloud@v2
  with:
    install_components: 'cloud-firestore-emulator'

- name: Run tests
  run: pytest

The emulator runs locally and requires no GCP credentials. Authentication is irrelevant to this use case, but the warning appears on every workflow run, creating noise in CI logs.

Proposal

Add an optional input (e.g., skip_auth_check: true) to suppress the authentication warning when users knowingly don't need authentication.

Alternatively, the action could skip the auth check automatically when only install_components is specified and no other gcloud-dependent inputs (like project_id) are provided.

Related
  • #670 — similar request, but for a different use case (self-hosted runners with ADC). The maintainer's response was that warnings can be ignored, but for component-only installations the warning is particularly misleading since auth is genuinely unnecessary.
Vorherrschende Sprache
TypeScript
Sterne
1.9k
Forks
534
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus google-github-actions/setup-gcloud

Alle Issues in google-github-actions/setup-gcloud

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.