Testkube Doc: refine test doc for content.type

[gberche-orange]

Pull request description

Doc: refine schema for content.type

Extracted from https://github.com/kubeshop/testkube/blob/cca3c13629078891f269f691e1050ae5adb99d5a/docs/docs/test-types/prebuilt-executor.md?plain=1#L60-L65

Checklist (choose whats happened)

• breaking change! (describe)
• tested locally
• tested on cluster
• added new dependencies
• updated the docs
• added a test

Breaking changes

Changes

Fixes

[vsukhin]

actually, we also support git type, it automatically detects file or dirs

[gberche-orange]

thanks, I gave it a try into 12313d9 does it properly captures current behavior ?

[gberche-orange]

BTW, is it intended that the sparse checkout leaves the /data/repo with root of the git repo and not the subdir as new root ?

E.g. with path: micro-depls/00-core-connectivity-k8s/k8s-config/manifests/02-testkube-executors the container currently sees the following

6481e45d62b70b1853b6a89c-kzm8b:~# tree /data/repo/
/data/repo/
└── micro-depls
    └── 00-core-connectivity-k8s
        └── k8s-config
            └── manifests
                └── 02-testkube-executors
                    ├── 02-testkube-sample-tests-kuttl-test-git-repo.yaml
...
                    └── last_rendered_kustomization.yaml

[vsukhin]

internally, we already trreat everything as git. yes, the idea is to support monorepo as well

[gberche-orange]

thanks,

BTW, is it intended that the sparse checkout leaves the /data/repo with root of the git repo and not the subdir as new root ?

sorry I had missed the workingDir field which answers my question

                        workingDir:
                          description: if provided we checkout the whole repository
                            and run test from this directory
                          type: string
``