kustomize

GitHub Action to build manifests based on Kustomize.

Usage

name: Example

on:
  - push
  - pull_request

jobs:
  test:
    runs-on: ubuntu-latest

    steps:
      - uses: actions/checkout@v2

      - uses: actionhippie/kustomize@v1
        with:
          version: 4.4.0

Inputs

args

Override all kustomize arguments

target

Optional path to write output into

workingdir

Switch into this directory before execution

stack_trace

Print a stack-trace on error

enable_alpha_plugins

Enable Kustomize alpha plugins

enable_exec

Enable support for exec functions

enable_helm

Enable Helm inflator generator

enable_managedby_label

Inject app.kubernetes.io/managed-by labels

enable_star

Enable support for starlark functions

load_restrictor

Override load restrictions

reorder

Reorder resources before output

path

Path to read, defaults to current directory

print

Print messages directly, defaults to true

version

Use a specific version of Kustomize

helm

Use a specific version of Helm

ksops

Use a specific version of Ksops

gpgkey

Private GnuPG key for KSOPS integration

Outputs

manifest

Generated manifest for Kubernetes

Security

If you find a security issue please contact thomas@webhippie.de first.

Contributing

Generally we are following conventional commits when we apply changes. That way we are able to generate proper changelogs for every release. Please use always pull requests to integrate new functionalities or to fix issues.

For the release process we are following semantic versioning which clearly indicates if a new version just resolves bugs, includes new features or even includes breaking changes.

After installing the tools via mise install as described above set up the pre-commit hooks so they run automatically on every commit:

prek install --hook-type pre-commit --hook-type commit-msg

prek is managed by mise and will be available after mise install.

If you have changed something on the source you should simply commit following the mentioned conventions:

git checkout -b feat/new-feature
git add --all
git commit -m 'feat: added awesome new feature'
git push --set-upstream origin feat/new-feature

After pushing your changes into the Git repository you should create a pull request on GitHub. If the pull request have been merged and everything built fine it will also create automatically a new release at least once a week.

Authors

• Thomas Boerger

License

Apache-2.0

Copyright

Copyright (c) 2021 Thomas Boerger <thomas@webhippie.de>