Option to suppress auth warning when using install_components without authentication
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 38/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- github-actions, google-cloud, typescript
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 1.9k
- Forks
- 534
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de google-github-actions/setup-gcloud
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
google-github-actions/setup-gcloud#735 · 1 reacción ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 52/100
google-github-actions/setup-gcloud#734 · 1 comentario · 2 reacciones ·
-
Option to install numpyAbiertoenhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
Todos los issues de google-github-actions/setup-gcloud
Issues similares
-
awaiting-response bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
wildcard/caro#1562 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
supadata-ai/mcp#27 ·
-
content
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
cosimochellini/one-piece-zero-spoiler#516 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
capricorn86/happy-dom#2485 ·
Los mantenedores suelen responder en 2 días
-
lane: fast
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
unicef/adt-studio#946 ·
Los mantenedores suelen responder en 2 días