Repository navigation
RINF-55 Los despliegues leen sus secretos de Bitwarden Secrets Manager - #9
Merged
Merged
Conversation
The Secrets step of deploy-laravel, deploy-wordpress and deploy-static runs `core.sh secrets`: with BWS_ACCESS_TOKEN it reads the actions project with bws (EU region, pinned and checksummed), takes the most specific key (NAME__COMPONENT__ENVIRONMENT, NAME__COMPONENT, NAME), masks each value and leaves it in GITHUB_ENV for the next steps. A name still missing in Bitwarden falls back to the GitHub secret with a warning; without a token everything comes from GitHub as before. In deploy-static the step moves after the build, so the build never sees a secret. OS-Ref: D-109 Refs: RINF-55 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fk5Z87ufMJBhy7xKHpFu4W
|
Linked to Plane Work Item(s) References This comment was auto-generated by Plane |
Refs: RINF-55 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Fk5Z87ufMJBhy7xKHpFu4W
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Sergio · project thread
Resumen
Tarea
ci-*.yml, pero esos no leen secretos: los que leen son losdeploy-*.yml, y son los que cambia esta PR.Qué cambia
deploy-laravel,deploy-wordpress,deploy-static) leen sus secretos de Bitwarden Secrets Manager, proyectoactions, región EU. En GitHub, cada repositorio deja soloBWS_ACCESS_TOKEN.PLOI_DEPLOY_WEBHOOK__ACME_PORTAL__PRODUCTION, luegoPLOI_DEPLOY_WEBHOOK__ACME_PORTALy luegoPLOI_DEPLOY_WEBHOOK.BWS_ACCESS_TOKEN, todo funciona igual que hoy, así que fusionar no rompe ningún despliegue.Cómo probarlo en 2 minutos
test(ShellCheck, 119 pruebas detests/deploy-core.test.shcon unbwsfalso, y los workflows parsean).BWS_ACCESS_TOKEN(de la cuenta de máquinaactions-deploy) en el entorno staging de un repositorio que despliegue.Criterios de aceptación
deploy-static, el build ya no ve ningún secreto: el paso Secrets va después del build.Riesgos
bws, el CLI oficial de Bitwarden (bitwarden/sdk-sm), ya nombrado en D-109 y en RCOR-44. La alternativa,bitwarden/sm-action, se descartó porque pide un UUID por secreto en cada workflow; el hilo de Motor usa tambiénbwspor nombre.core.shy es la misma que usa rasgo-motor#175; con otraBWS_VERSIONse compara contra la suma de su release. Desde esta sesión no pude descargar la release: si el nombre del zip no coincide, el paso falla con un mensaje claro y no despliega.env.Xen lugar desecrets.X. Los workflows se llaman a@main, así que el cambio llega a todos los despliegues a la vez.Capturas
No aplica.
Tiempo
Pendiente de Sergio: la hija 1 (pasos): el proyecto
actions, la cuenta de máquina y su token, y los secretos con las claves de arriba.https://claude.ai/code/session_01Fk5Z87ufMJBhy7xKHpFu4W
Generated by Claude Code