From 2805268826fa01a34477d010e1d0d8b1dd034b94 Mon Sep 17 00:00:00 2001 From: Marcus Date: Fri, 23 Jan 2026 17:19:22 -0300 Subject: [PATCH] ci: configura deploy automatico para k3s --- .forgejo/workflows/deploy.yaml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/.forgejo/workflows/deploy.yaml b/.forgejo/workflows/deploy.yaml index 518065f..56bd2ae 100644 --- a/.forgejo/workflows/deploy.yaml +++ b/.forgejo/workflows/deploy.yaml @@ -76,24 +76,26 @@ jobs: - name: Deploy to K3s run: | - # 1. SALVA O CONFIG E EXPORTA A VARIÁVEL + # 1. CRIA O ARQUIVO E EXPORTA NO MESMO BLOCO echo "${{ secrets.KUBECONFIG }}" > /tmp/kubeconfig chmod 600 /tmp/kubeconfig - export KUBECONFIG=/tmp/kubeconfig # ISSO AQUI MATA O ERRO DE LOCALHOST + export KUBECONFIG=/tmp/kubeconfig - # 2. DELETA E RECRIA OS SEGREDO + # 2. TESTA A CONEXÃO + echo "Testando conexão com o cluster..." + kubectl cluster-info || exit 1 + + # 3. ATUALIZA OS SEGREDO kubectl -n gohorsejobsdev delete secret backend-secrets --ignore-not-found kubectl -n gohorsejobsdev create secret generic backend-secrets \ --from-literal=DATABASE_URL="${{ vars.DATABASE_URL }}" \ --from-literal=JWT_SECRET="${{ vars.JWT_SECRET }}" \ --from-literal=MTU="${{ vars.MTU }}" - # 3. APLICA OS MANIFESTOS + # 4. APLICA E RESTARTA kubectl apply -f k8s/dev/ -n gohorsejobsdev - - # 4. RESTARTA OS DEPLOYMENTS kubectl -n gohorsejobsdev rollout restart deployment gohorse-backend-dev kubectl -n gohorsejobsdev rollout restart deployment gohorse-backoffice-dev - # 5. VERIFICA O STATUS FINAL + # 5. STATUS FINAL kubectl -n gohorsejobsdev rollout status deployment gohorse-backend-dev \ No newline at end of file