generated from openmcp-project/repository-template
-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
in case there is an error on kustomize, while kustomize-listing is disable, the k8s-manifest-templating will still run. it does report on the job log and on the summary annotation, but it does not mark the job state as failed
kustomize-listing:
enable: false
this error is reported in the job log and the job summary as annotation
pr-status-check / Helm Checks❌ Kustomize build failed for cluster/argocd-config: Error: Command failed: kubectl kustomize /home/runner/work/temp-test-suite-k8sconfig/temp-test-suite-k8sconfig/cluster/argocd-config error: accumulating resources: accumulation err='accumulating resources from 'modified.yaml': evalsymlink failure on '/home/runner/work/temp-test-suite-k8sconfig/temp-test-suite-k8sconfig/cluster/argocd-config/modified.yaml' : lstat /home/runner/work/temp-test-suite-k8sconfig/temp-test-suite-k8sconfig/cluster/argocd-config/modified.yaml: no such file or directory': must build at directory: not a valid directory: evalsymlink failure on '/home/runner/work/temp-test-suite-k8sconfig/temp-test-suite-k8sconfig/cluster/argocd-config/modified.yaml' : lstat /home/runner/work/temp-test-suite-k8sconfig/temp-test-suite-k8sconfig/cluster/argocd-config/modified.yaml: no such file or directory
not a big deal, but I would expect the manifest-generate job status is set to failed in case there is an error.

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels