kubectl kustomize errored: error: specify one path to kustomization.yaml

[prestonvanloon]

name: kustomization
on: push
    
env:
  DATREE_TOKEN: ${{ secrets.DATREE_TOKEN }} 

jobs:
  kustomize_check:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v2
      - name: Run Datree Policy Check on Kustomize
        uses: datreeio/action-datree@69aaff54675fdbda959740657d0fc81be9afd4fc
        with:
          path: 'cluster/default/**'
          isKustomization: true
          cliArguments: '--policy Github --ignore-missing-schemas --output simple'

kubectl kustomize errored: error: specify one path to kustomization.yaml

It passes when using commit 460c784

[hadar-co]

Hi @prestonvanloon :)
We recently fixed an issue regarding globs (**), where they did not work recursively.
So now when you specify a path like 'cluster/default/**' all subdirectories will also be parsed. I am guessing that there is another "kustomization.yaml" somewhere inside your folder hierarchy, which is causing this error.

Is there a reason you're using a glob for this? When using Datree to run a policy check against a Kustomization, all you need to provide is the path to the dir containing the "kustomization.yaml" file. In your case - if, for example, that file is in the dir 'cluster/default/' then that is what you should pass to the path, without the '**'.

Let me know if that helps:)

[hadar-co]

Hi @prestonvanloon, Have you had a chance to see if this resolves your issue?:)

[Taranpreet26311]

Hey @hadar-co, the issue seems to be we have nested kustomized directories. We are using Gitops with Kustomized, the structure consists of the a root kustomized directory and component's kuztomized. We specify each parent directory in parent kustomized.yaml and the files for particular component in component's root kustomized.yaml. This is an example of our repository structure https://github.com/fluxcd/flux2-kustomize-helm-example/tree/main/infrastructure

[hadar-co]

Hi @Taranpreet26311, this is the structure that the CLI expects, so in order to test the example you wrote here, you would set the path to "./infrastructure". Under the hood, Datree runs "kustomize build" on this directory and runs a pollicy check against the generated YAMLs.
However, from @prestonvanloon's comment, I understand that you added "**" to the path, which will cause the OS to recursively list all of the subdirectories as well, which I suspect is the cause of the error you're getting.
Can you try setting your parent kustomization folder as the path of the action (without "**") so we can test this theory?:)

[Taranpreet26311]

Hey @hadar-co this seems to have fixed the issue. Thanks for the assistance!

[hadar-co]

Glad to hear, No problem:)