feat: inject secrets via infisical run at container startup - #44
Merged
Merged
Conversation
|
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.



Objetivo
A integração nativa Infisical↔Render (Secret Sync) esbarrou em limite do plano ao precisar de várias pastas por serviço. Migrando pra injeção via
infisical rundentro do container, autenticado por Machine Identity (Universal Auth) — isso também corrige o crash atual (Cannot load driver class: org.postgresql.Driver), causado pelas env vars de banco não chegarem no serviço.Alterações
entrypoint.sh: autentica no Infisical via Universal Auth (INFISICAL_CLIENT_ID/INFISICAL_CLIENT_SECRET) e rodainfisical runpuxando/database,/redis,/cloudinary,/google,/auth,/otel,/service-urlsantes de subir o jar.Dockerfile: instala o CLI do Infisical na imagem final e troca oENTRYPOINTdejava -jar app.jarproentrypoint.sh.Endpoints afetados
Sem endpoints afetados
Banco de Dados
Como testar
Configurar
INFISICAL_CLIENT_ID/INFISICAL_CLIENT_SECRETcomo env vars do serviço no Render (Machine Identityrender, acesso de leitura emqa) e fazer o deploy — confirmar que o serviço sobe sem o erro de datasource.Evidências
Sem evidências visuais
Closes #