Skip to content

GitHub action to Kustomize GitOps manifests used in ArgoCD

Notifications You must be signed in to change notification settings

platformbuilders/github-actions-kustomize-argocd-manifests

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

64 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Kustomize ArgoCD manifests

GitHub action used kustomize applications manifests

Inputs

  • gitops-repo-name: The name of GitOps git repository;
  • gitops-repo-url: The URL of GitOps repository;
  • gh_access_token: The access token of GitOps repository;
  • gcp_project_id_prod: The GCP project ID;
  • app_id: The App ID;
  • github_actor: The github commit actor ID;

OBS.: All inputs are required

Outputs

There are no outputs for this action

Example usage

      - name: Kustomize step
        uses: platformbuilders/github-actions-kustomize-argocd-manifests@master
        with:
          gitops-repo-name: '<gitops-repo-name>'
          gitops-repo-url: '< gitops-repo-url >'
          gh_access_token: ${{ secrets.GH_ACCESS_TOKEN }}
          gcp_project_id_prod: ${{ secrets.GCP_PROJECT_ID_PROD }}
          app_id: ${{ secrets.APP_ID }}
          github_actor: ${{ github.actor }}

How to send updates?

If you wants to update or make changes in module code you should use the develop branch of this repository, you can test your module changes passing the @develop in module calling. Ex.:

      # Example using this actions
      - name: MVN Package
        uses: platformbuilders/github-actions-build@develop

After execute all tests you can open a pull request to the master branch.

About

GitHub action to Kustomize GitOps manifests used in ArgoCD

Resources

Stars

Watchers

Forks

Packages

No packages published

Contributors 3

  •  
  •  
  •