Let’s dive in step-by-step! <\/p>\n\n\n\n
Prerequisites<\/strong><\/h2>\n\n\n\nBefore you begin, make sure you have:<\/p>\n\n\n\n
\n- A GitHub repository set up<\/li>\n\n\n\n
- Basic knowledge of Docker and GitHub Actions<\/li>\n\n\n\n
- GitHub CLI<\/a> installed (for managing secrets)<\/li>\n\n\n\n
- Docker installed on your machine<\/li>\n\n\n\n
- A working ArgoCD installation<\/li>\n<\/ul>\n\n\n\n
Step 1: Setting Up Your Repository & Folder Structure<\/strong><\/h2>\n\n\n\nAssume you have a repository with multiple microservices, each with its own Dockerfile<\/mark>. Your repository might look like this:<\/p>\n\n\n\n![\"Example](\"https:\/\/beon.tech\/blog\/wp-content\/uploads\/2025\/07\/image-1.png\")
<\/figure>\n\n\n\nHere, our GitHub Action will only build images for the services that changed<\/strong>.<\/p>\n\n\n\nStep 2: Creating the Dynamic GitHub Action Workflow<\/strong><\/h2>\n\n\n\nWe need to first detect which microservices in the app\/ folder have changed. We’ll do this in a dedicated job that creates a dynamic matrix for the build job.<\/p>\n\n\n\n
Create the file <\/mark>.<\/mark>github\/workflows\/docker-build.yml<\/mark> <\/mark>with the following content:<\/p>\n\n\n\nname: Docker Build for Changed Microservices\n\n\non:\n push:\n paths:\n - 'app\/**'\n\n\njobs:\n detect:\n name: Detect Changed Services\n runs-on: ubuntu-latest\n outputs:\n matrix: ${{ steps.get-matrix.outputs.matrix }}\n steps:\n - name: Checkout Repository Code\n uses: actions\/checkout@v3\n with:\n fetch-depth: 0\n\n\n - name: Determine Changed Services\n id: get-matrix\n shell: bash\n run: |\n cd $GITHUB_WORKSPACE\n echo \"Detecting changes...\"\n CHANGED_FOLDERS=$(git diff --name-only ${{ github.event.before }} ${{ github.sha }} app | awk -F\/ '!($2 ~ \/^(Dockerfile|SomeFileYouDoNotWantToDetect|Makefile)$\/) {print $2}' | sort -u | xargs)\n echo \"Changed folders: $CHANGED_FOLDERS\"\n\n\n matrix=\"{\\\"include\\\": [\"\n first=1\n for service in $CHANGED_FOLDERS; do\n if [ -f \"app\/${service}\/Dockerfile\" ]; then\n if [ $first -eq 0 ]; then\n matrix+=\",\"\n fi\n matrix+=\"{\\\"service\\\": \\\"${service}\\\"}\"\n first=0\n fi\n done\n matrix+=\"]}\"\n \n echo \"Matrix for build job: $matrix\"\n echo \"matrix=$matrix\" >> $GITHUB_OUTPUT\n\n\n - name: Validate Matrix\n if: ${{ fromJson(steps.get-matrix.outputs.matrix).include[0] == null }}\n run: |\n echo \"Output from previous step:\"\n echo \"${{ fromJson(steps.get-matrix.outputs.matrix).include.length }}\"\n echo \"${{ steps.get-matrix.outputs.matrix }}\"\n echo \"No services with a Dockerfile were changed. Exiting gracefully.\"\n exit 0\n\n\n build:\n name: Build & Push Docker Images\n needs: detect\n runs-on: ubuntu-latest\n if: ${{ fromJson(needs.detect.outputs.matrix).include[0] != null }}\n strategy:\n matrix: ${{ fromJson(needs.detect.outputs.matrix) }}\n env:\n DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}\n DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}\n steps:\n - name: Checkout Repository\n uses: actions\/checkout@v3\n\n\n - name: Set up Docker Buildx\n uses: docker\/setup-buildx-action@v2\n\n\n - name: Login to DockerHub\n uses: docker\/login-action@v2\n with:\n registry: ghcr.io\n username: juliolugo96 # Change to your Github username\n password: ${{ github.token }}\n\n\n - name: Build and Push Docker Image for ${{ matrix.service }}\n uses: docker\/build-push-action@v4\n with:\n context: .\/app\/${{ matrix.service }}\n file: .\/app\/${{ matrix.service }}\/Dockerfile\n push: true\n tags: ghcr.io\/juliolugo96\/${{ matrix.service }}:${{ github.sha }},ghcr.io\/juliolugo96\/${{ matrix.service }}:latest\n\n\n # - name: Trigger ArgoCD Deployment for ${{ matrix.service }}\n # env:\n # ARGOCD_TOKEN: ${{ secrets.ARGOCD_TOKEN }}\n # ARGOCD_SERVER: ${{ secrets.ARGOCD_SERVER }}\n # run: |\n # curl -H \"Authorization: Bearer ${ARGOCD_TOKEN}\" -X POST \"https:\/\/${ARGOCD_SERVER}\/api\/v1\/applications\/your-argocd-app-${{ matrix.service }}\/sync\"\n<\/code><\/pre>\n\n\n\n\n<\/div><\/div><\/div>\n<\/div><\/div><\/div>\n\n\n\nHow It Works:<\/strong><\/h3>\n\n\n\nSuch a beautiful yet simple code, right? Let me show you how it works:<\/p>\n\n\n\n
\n- Detect Job:<\/strong>
<\/strong>\n\n- Checks out your repository.<\/li>\n\n\n\n
- Uses git diff to determine which files in app\/ changed.<\/li>\n\n\n\n
- Extracts the service names (assumes structure app\/<service>\/…).<\/li>\n\n\n\n
- Validates that a Dockerfile exists in each service folder.<\/li>\n\n\n\n
- Outputs a JSON matrix containing only the changed services.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Build Job:<\/strong>
<\/strong>\n\n- Runs for each service in the matrix.<\/li>\n\n\n\n
- Checks out the repository and sets up Docker Buildx.<\/li>\n\n\n\n
- Logs into GHCR using your secrets.<\/li>\n\n\n\n
- Builds and pushes the Docker image for the specific service.<\/li>\n\n\n\n
- Triggers an ArgoCD sync for the corresponding application.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
Note:<\/strong> Adjust the Docker image tags and ArgoCD endpoints to match your environment.<\/p>\n\n\n\nStep 3: Defining Environment Variables & Secrets<\/strong><\/h2>\n\n\n\nSince our workflow relies on environment variables and secrets, you can automate their setup using the following shell script with GitHub CLI.<\/p>\n\n\n\n
\nsetup-secrets.sh<\/mark><\/strong><\/h3>\n\n\n\n#!\/bin\/bash<\/mark><\/p>\n\n\n\n# Ensure you are logged in with GitHub CLI: gh auth login<\/mark><\/p>\n<\/div>\n\n\n\nREPO=”your-github-username\/your-repository”<\/mark><\/p>\n\n\n\n\n# Set DockerHub credentials<\/mark><\/p>\n\n\n\ngh secret set DOCKER_USERNAME –repo $REPO –body “your-dockerhub-username”<\/mark><\/p>\n\n\n\ngh secret set DOCKER_PASSWORD –repo $REPO –body “your-dockerhub-password”<\/mark><\/p>\n<\/div>\n\n\n\n\n# Set ArgoCD credentials<\/mark><\/p>\n\n\n\ngh secret set ARGOCD_TOKEN –repo $REPO –body “your-argocd-token”<\/mark><\/p>\n\n\n\ngh secret set ARGOCD_SERVER –repo $REPO –body “your-argocd-server-address”<\/mark><\/p>\n\n\n\necho “Secrets have been set for $REPO!”<\/mark><\/p>\n\n\n\n<\/p>\n<\/div>\n\n\n\n
Run this script from your terminal:<\/mark><\/p>\n\n\n\n<\/p>\n\n\n\n
\nchmod +x setup-secrets.sh<\/mark><\/p>\n\n\n\n.\/setup-secrets.sh<\/mark><\/p>\n<\/div>\n\n\n\nStep 4: Deploying with ArgoCD<\/strong><\/h2>\n\n\n\nOnce a Docker image is built and pushed, our workflow triggers an ArgoCD sync. This sync uses a simple curl command to notify ArgoCD that the application (per microservice) has been updated.<\/p>\n\n\n\n
If your deployment strategy is more complex, consider:<\/p>\n\n\n\n
\n- Using the ArgoCD CLI<\/a> action.<\/li>\n\n\n\n
- Creating dedicated ArgoCD projects for each microservice.<\/li>\n<\/ul>\n\n\n\n
Check ArgoCD’s documentation<\/a> for more advanced deployment configurations.<\/p>\n\n\n\nWrapping Up<\/strong><\/h2>\n\n\n\nCongratulations!<\/strong> You now have a fully automated CI\/CD pipeline that:<\/p>\n\n\n\n\n- Detects changes<\/strong> in individual microservices within the app\/ folder.<\/li>\n\n\n\n
- Builds and pushes Docker images<\/strong> only for the changed services.<\/li>\n\n\n\n
- Triggers deployments<\/strong> via ArgoCD for each updated microservice.<\/li>\n<\/ul>\n\n\n\n
This setup helps you efficiently manage multiple microservices within a single repository. Customize and expand the workflow to suit your project\u2019s needs, and enjoy a smoother DevOps experience! <\/p>\n\n\n\n
Want to see the full code in action? Check out the repository <\/a>.<\/p>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
Step 1: Setting Up Your Repository & Folder Structure<\/strong><\/h2>\n\n\n\nAssume you have a repository with multiple microservices, each with its own Dockerfile<\/mark>. Your repository might look like this:<\/p>\n\n\n\n<\/figure>\n\n\n\nHere, our GitHub Action will only build images for the services that changed<\/strong>.<\/p>\n\n\n\nStep 2: Creating the Dynamic GitHub Action Workflow<\/strong><\/h2>\n\n\n\nWe need to first detect which microservices in the app\/ folder have changed. We’ll do this in a dedicated job that creates a dynamic matrix for the build job.<\/p>\n\n\n\n
Create the file <\/mark>.<\/mark>github\/workflows\/docker-build.yml<\/mark> <\/mark>with the following content:<\/p>\n\n\n\nname: Docker Build for Changed Microservices\n\n\non:\n push:\n paths:\n - 'app\/**'\n\n\njobs:\n detect:\n name: Detect Changed Services\n runs-on: ubuntu-latest\n outputs:\n matrix: ${{ steps.get-matrix.outputs.matrix }}\n steps:\n - name: Checkout Repository Code\n uses: actions\/checkout@v3\n with:\n fetch-depth: 0\n\n\n - name: Determine Changed Services\n id: get-matrix\n shell: bash\n run: |\n cd $GITHUB_WORKSPACE\n echo \"Detecting changes...\"\n CHANGED_FOLDERS=$(git diff --name-only ${{ github.event.before }} ${{ github.sha }} app | awk -F\/ '!($2 ~ \/^(Dockerfile|SomeFileYouDoNotWantToDetect|Makefile)$\/) {print $2}' | sort -u | xargs)\n echo \"Changed folders: $CHANGED_FOLDERS\"\n\n\n matrix=\"{\\\"include\\\": [\"\n first=1\n for service in $CHANGED_FOLDERS; do\n if [ -f \"app\/${service}\/Dockerfile\" ]; then\n if [ $first -eq 0 ]; then\n matrix+=\",\"\n fi\n matrix+=\"{\\\"service\\\": \\\"${service}\\\"}\"\n first=0\n fi\n done\n matrix+=\"]}\"\n \n echo \"Matrix for build job: $matrix\"\n echo \"matrix=$matrix\" >> $GITHUB_OUTPUT\n\n\n - name: Validate Matrix\n if: ${{ fromJson(steps.get-matrix.outputs.matrix).include[0] == null }}\n run: |\n echo \"Output from previous step:\"\n echo \"${{ fromJson(steps.get-matrix.outputs.matrix).include.length }}\"\n echo \"${{ steps.get-matrix.outputs.matrix }}\"\n echo \"No services with a Dockerfile were changed. Exiting gracefully.\"\n exit 0\n\n\n build:\n name: Build & Push Docker Images\n needs: detect\n runs-on: ubuntu-latest\n if: ${{ fromJson(needs.detect.outputs.matrix).include[0] != null }}\n strategy:\n matrix: ${{ fromJson(needs.detect.outputs.matrix) }}\n env:\n DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}\n DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}\n steps:\n - name: Checkout Repository\n uses: actions\/checkout@v3\n\n\n - name: Set up Docker Buildx\n uses: docker\/setup-buildx-action@v2\n\n\n - name: Login to DockerHub\n uses: docker\/login-action@v2\n with:\n registry: ghcr.io\n username: juliolugo96 # Change to your Github username\n password: ${{ github.token }}\n\n\n - name: Build and Push Docker Image for ${{ matrix.service }}\n uses: docker\/build-push-action@v4\n with:\n context: .\/app\/${{ matrix.service }}\n file: .\/app\/${{ matrix.service }}\/Dockerfile\n push: true\n tags: ghcr.io\/juliolugo96\/${{ matrix.service }}:${{ github.sha }},ghcr.io\/juliolugo96\/${{ matrix.service }}:latest\n\n\n # - name: Trigger ArgoCD Deployment for ${{ matrix.service }}\n # env:\n # ARGOCD_TOKEN: ${{ secrets.ARGOCD_TOKEN }}\n # ARGOCD_SERVER: ${{ secrets.ARGOCD_SERVER }}\n # run: |\n # curl -H \"Authorization: Bearer ${ARGOCD_TOKEN}\" -X POST \"https:\/\/${ARGOCD_SERVER}\/api\/v1\/applications\/your-argocd-app-${{ matrix.service }}\/sync\"\n<\/code><\/pre>\n\n\n\n\n<\/div><\/div><\/div>\n<\/div><\/div><\/div>\n\n\n\nHow It Works:<\/strong><\/h3>\n\n\n\nSuch a beautiful yet simple code, right? Let me show you how it works:<\/p>\n\n\n\n
\n- Detect Job:<\/strong>
<\/strong>\n\n- Checks out your repository.<\/li>\n\n\n\n
- Uses git diff to determine which files in app\/ changed.<\/li>\n\n\n\n
- Extracts the service names (assumes structure app\/<service>\/…).<\/li>\n\n\n\n
- Validates that a Dockerfile exists in each service folder.<\/li>\n\n\n\n
- Outputs a JSON matrix containing only the changed services.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Build Job:<\/strong>
<\/strong>\n\n- Runs for each service in the matrix.<\/li>\n\n\n\n
- Checks out the repository and sets up Docker Buildx.<\/li>\n\n\n\n
- Logs into GHCR using your secrets.<\/li>\n\n\n\n
- Builds and pushes the Docker image for the specific service.<\/li>\n\n\n\n
- Triggers an ArgoCD sync for the corresponding application.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
Note:<\/strong> Adjust the Docker image tags and ArgoCD endpoints to match your environment.<\/p>\n\n\n\nStep 3: Defining Environment Variables & Secrets<\/strong><\/h2>\n\n\n\nSince our workflow relies on environment variables and secrets, you can automate their setup using the following shell script with GitHub CLI.<\/p>\n\n\n\n
\nsetup-secrets.sh<\/mark><\/strong><\/h3>\n\n\n\n#!\/bin\/bash<\/mark><\/p>\n\n\n\n# Ensure you are logged in with GitHub CLI: gh auth login<\/mark><\/p>\n<\/div>\n\n\n\nREPO=”your-github-username\/your-repository”<\/mark><\/p>\n\n\n\n\n# Set DockerHub credentials<\/mark><\/p>\n\n\n\ngh secret set DOCKER_USERNAME –repo $REPO –body “your-dockerhub-username”<\/mark><\/p>\n\n\n\ngh secret set DOCKER_PASSWORD –repo $REPO –body “your-dockerhub-password”<\/mark><\/p>\n<\/div>\n\n\n\n\n# Set ArgoCD credentials<\/mark><\/p>\n\n\n\ngh secret set ARGOCD_TOKEN –repo $REPO –body “your-argocd-token”<\/mark><\/p>\n\n\n\ngh secret set ARGOCD_SERVER –repo $REPO –body “your-argocd-server-address”<\/mark><\/p>\n\n\n\necho “Secrets have been set for $REPO!”<\/mark><\/p>\n\n\n\n<\/p>\n<\/div>\n\n\n\n
Run this script from your terminal:<\/mark><\/p>\n\n\n\n<\/p>\n\n\n\n
\nchmod +x setup-secrets.sh<\/mark><\/p>\n\n\n\n.\/setup-secrets.sh<\/mark><\/p>\n<\/div>\n\n\n\nStep 4: Deploying with ArgoCD<\/strong><\/h2>\n\n\n\nOnce a Docker image is built and pushed, our workflow triggers an ArgoCD sync. This sync uses a simple curl command to notify ArgoCD that the application (per microservice) has been updated.<\/p>\n\n\n\n
If your deployment strategy is more complex, consider:<\/p>\n\n\n\n
\n- Using the ArgoCD CLI<\/a> action.<\/li>\n\n\n\n
- Creating dedicated ArgoCD projects for each microservice.<\/li>\n<\/ul>\n\n\n\n
Check ArgoCD’s documentation<\/a> for more advanced deployment configurations.<\/p>\n\n\n\nWrapping Up<\/strong><\/h2>\n\n\n\nCongratulations!<\/strong> You now have a fully automated CI\/CD pipeline that:<\/p>\n\n\n\n\n- Detects changes<\/strong> in individual microservices within the app\/ folder.<\/li>\n\n\n\n
- Builds and pushes Docker images<\/strong> only for the changed services.<\/li>\n\n\n\n
- Triggers deployments<\/strong> via ArgoCD for each updated microservice.<\/li>\n<\/ul>\n\n\n\n
This setup helps you efficiently manage multiple microservices within a single repository. Customize and expand the workflow to suit your project\u2019s needs, and enjoy a smoother DevOps experience! <\/p>\n\n\n\n
Want to see the full code in action? Check out the repository <\/a>.<\/p>\n\n\n\n<\/p>\n","protected":false},"excerpt":{"rendered":"
<\/figure>\n\n\n\nHere, our GitHub Action will only build images for the services that changed<\/strong>.<\/p>\n\n\n\n We need to first detect which microservices in the app\/ folder have changed. We’ll do this in a dedicated job that creates a dynamic matrix for the build job.<\/p>\n\n\n\n Create the file <\/mark>.<\/mark>github\/workflows\/docker-build.yml<\/mark> <\/mark>with the following content:<\/p>\n\n\n\n Such a beautiful yet simple code, right? Let me show you how it works:<\/p>\n\n\n\n Note:<\/strong> Adjust the Docker image tags and ArgoCD endpoints to match your environment.<\/p>\n\n\n\n Since our workflow relies on environment variables and secrets, you can automate their setup using the following shell script with GitHub CLI.<\/p>\n\n\n\n #!\/bin\/bash<\/mark><\/p>\n\n\n\n # Ensure you are logged in with GitHub CLI: gh auth login<\/mark><\/p>\n<\/div>\n\n\n\n REPO=”your-github-username\/your-repository”<\/mark><\/p>\n\n\n\n # Set DockerHub credentials<\/mark><\/p>\n\n\n\n gh secret set DOCKER_USERNAME –repo $REPO –body “your-dockerhub-username”<\/mark><\/p>\n\n\n\n gh secret set DOCKER_PASSWORD –repo $REPO –body “your-dockerhub-password”<\/mark><\/p>\n<\/div>\n\n\n\n # Set ArgoCD credentials<\/mark><\/p>\n\n\n\n gh secret set ARGOCD_TOKEN –repo $REPO –body “your-argocd-token”<\/mark><\/p>\n\n\n\n gh secret set ARGOCD_SERVER –repo $REPO –body “your-argocd-server-address”<\/mark><\/p>\n\n\n\n echo “Secrets have been set for $REPO!”<\/mark><\/p>\n\n\n\n <\/p>\n<\/div>\n\n\n\n Run this script from your terminal:<\/mark><\/p>\n\n\n\n <\/p>\n\n\n\n chmod +x setup-secrets.sh<\/mark><\/p>\n\n\n\n .\/setup-secrets.sh<\/mark><\/p>\n<\/div>\n\n\n\n Once a Docker image is built and pushed, our workflow triggers an ArgoCD sync. This sync uses a simple curl command to notify ArgoCD that the application (per microservice) has been updated.<\/p>\n\n\n\n If your deployment strategy is more complex, consider:<\/p>\n\n\n\n Check ArgoCD’s documentation<\/a> for more advanced deployment configurations.<\/p>\n\n\n\n Congratulations!<\/strong> You now have a fully automated CI\/CD pipeline that:<\/p>\n\n\n\n This setup helps you efficiently manage multiple microservices within a single repository. Customize and expand the workflow to suit your project\u2019s needs, and enjoy a smoother DevOps experience! <\/p>\n\n\n\n Want to see the full code in action? Check out the repository <\/a>.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":"Step 2: Creating the Dynamic GitHub Action Workflow<\/strong><\/h2>\n\n\n\n
name: Docker Build for Changed Microservices\n\n\non:\n push:\n paths:\n - 'app\/**'\n\n\njobs:\n detect:\n name: Detect Changed Services\n runs-on: ubuntu-latest\n outputs:\n matrix: ${{ steps.get-matrix.outputs.matrix }}\n steps:\n - name: Checkout Repository Code\n uses: actions\/checkout@v3\n with:\n fetch-depth: 0\n\n\n - name: Determine Changed Services\n id: get-matrix\n shell: bash\n run: |\n cd $GITHUB_WORKSPACE\n echo \"Detecting changes...\"\n CHANGED_FOLDERS=$(git diff --name-only ${{ github.event.before }} ${{ github.sha }} app | awk -F\/ '!($2 ~ \/^(Dockerfile|SomeFileYouDoNotWantToDetect|Makefile)$\/) {print $2}' | sort -u | xargs)\n echo \"Changed folders: $CHANGED_FOLDERS\"\n\n\n matrix=\"{\\\"include\\\": [\"\n first=1\n for service in $CHANGED_FOLDERS; do\n if [ -f \"app\/${service}\/Dockerfile\" ]; then\n if [ $first -eq 0 ]; then\n matrix+=\",\"\n fi\n matrix+=\"{\\\"service\\\": \\\"${service}\\\"}\"\n first=0\n fi\n done\n matrix+=\"]}\"\n \n echo \"Matrix for build job: $matrix\"\n echo \"matrix=$matrix\" >> $GITHUB_OUTPUT\n\n\n - name: Validate Matrix\n if: ${{ fromJson(steps.get-matrix.outputs.matrix).include[0] == null }}\n run: |\n echo \"Output from previous step:\"\n echo \"${{ fromJson(steps.get-matrix.outputs.matrix).include.length }}\"\n echo \"${{ steps.get-matrix.outputs.matrix }}\"\n echo \"No services with a Dockerfile were changed. Exiting gracefully.\"\n exit 0\n\n\n build:\n name: Build & Push Docker Images\n needs: detect\n runs-on: ubuntu-latest\n if: ${{ fromJson(needs.detect.outputs.matrix).include[0] != null }}\n strategy:\n matrix: ${{ fromJson(needs.detect.outputs.matrix) }}\n env:\n DOCKER_USERNAME: ${{ secrets.DOCKER_USERNAME }}\n DOCKER_PASSWORD: ${{ secrets.DOCKER_PASSWORD }}\n steps:\n - name: Checkout Repository\n uses: actions\/checkout@v3\n\n\n - name: Set up Docker Buildx\n uses: docker\/setup-buildx-action@v2\n\n\n - name: Login to DockerHub\n uses: docker\/login-action@v2\n with:\n registry: ghcr.io\n username: juliolugo96 # Change to your Github username\n password: ${{ github.token }}\n\n\n - name: Build and Push Docker Image for ${{ matrix.service }}\n uses: docker\/build-push-action@v4\n with:\n context: .\/app\/${{ matrix.service }}\n file: .\/app\/${{ matrix.service }}\/Dockerfile\n push: true\n tags: ghcr.io\/juliolugo96\/${{ matrix.service }}:${{ github.sha }},ghcr.io\/juliolugo96\/${{ matrix.service }}:latest\n\n\n # - name: Trigger ArgoCD Deployment for ${{ matrix.service }}\n # env:\n # ARGOCD_TOKEN: ${{ secrets.ARGOCD_TOKEN }}\n # ARGOCD_SERVER: ${{ secrets.ARGOCD_SERVER }}\n # run: |\n # curl -H \"Authorization: Bearer ${ARGOCD_TOKEN}\" -X POST \"https:\/\/${ARGOCD_SERVER}\/api\/v1\/applications\/your-argocd-app-${{ matrix.service }}\/sync\"\n<\/code><\/pre>\n\n\n\nHow It Works:<\/strong><\/h3>\n\n\n\n
\n
<\/strong>\n\n
<\/strong>\n\n
Step 3: Defining Environment Variables & Secrets<\/strong><\/h2>\n\n\n\n
setup-secrets.sh<\/mark><\/strong><\/h3>\n\n\n\n
Step 4: Deploying with ArgoCD<\/strong><\/h2>\n\n\n\n
\n
Wrapping Up<\/strong><\/h2>\n\n\n\n
\n