77. Go 1.22 fixed the most common for-loop trap #21
This file contains 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
| name: Deploy to production | |
| on: | |
| push: | |
| branches: [ main ] | |
| jobs: | |
| deploy: | |
| name: Build image | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Check out code | |
| uses: actions/checkout@v2 | |
| - uses: azure/setup-kubectl@v3 | |
| with: | |
| version: 'v1.28.2' | |
| id: install | |
| - name: Configure AWS credentials | |
| uses: aws-actions/configure-aws-credentials@v1 | |
| with: | |
| aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} | |
| aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} | |
| aws-region: ap-southeast-1 | |
| - name: Login to Amazon ECR | |
| id: login-ecr | |
| uses: aws-actions/amazon-ecr-login@v2 | |
| - name: Load secrets and save to app.env | |
| run: aws secretsmanager get-secret-value --secret-id simple_bank --query SecretString --output text | jq -r 'to_entries|map("\(.key)=\(.value)")|.[]' > app.env | |
| - name: Build, tag, and push docker image to Amazon ECR | |
| env: | |
| ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} | |
| ECR_REPOSITORY: simplebank | |
| IMAGE_TAG: ${{ github.sha }} | |
| run: | | |
| docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG -t $ECR_REGISTRY/$ECR_REPOSITORY:latest . | |
| docker push -a $ECR_REGISTRY/$ECR_REPOSITORY | |
| - name: Update kube config | |
| run: aws eks update-kubeconfig --name simple-bank --region ap-southeast-1 | |
| - name: Deploy image to Amazon EKS | |
| run: | | |
| kubectl apply -f eks/aws-auth.yaml | |
| kubectl rollout restart -f eks/deployment.yaml | |
| kubectl apply -f eks/service.yaml | |
| kubectl apply -f eks/issuer.yaml | |
| kubectl apply -f eks/ingress-nginx.yaml | |
| kubectl apply -f eks/ingress-http.yaml | |
| kubectl apply -f eks/ingress-grpc.yaml | |
| # เป็นที่ deployment.yaml เป็น rollout restart เนื่องจากว่าเมื่อใช้ apply ถ้าเราไม่ได้ไปแก้ content ใน deployment.yaml file มันมักจะไม่ pull image ใหม่มาไปรันที่ EKS | |
| # แต่ถ้า deploy ครั้งแรก ควรใช้ apply ที่ deployment.yaml นะ เพราะถ้าใช้ rollout restart ทั้งๆที่ยังไม่เคย apply มันจะ error |