Description of problem:

When there is an error on the siteconfig, it returns an error:
> kustomize build . --enable-alpha-plugins

1. Warning: 'bases' is deprecated. Please use 'resources' instead. Run 'kustomize edit fix' to update your Kustomization automatically.
   2023/12/20 19:19:19 Error could not create extra-manifest el8k-ztp-2.extra-manifests stat extra-manifests: no such file or directory
   2023/12/20 19:19:19 Error: could not build the entire SiteConfig defined by /tmp/kust-plugin-config-669417552: stat extra-manifests: no such file or directory
   but... it also outputs the original Siteconfig. This working together with ArgoCD means, that a Siteconfig object is created on the ArgocdApp. Of course, Argocd dont know what to do with an object of kind Siteconfig, because there does not exists this CRD.
   On ZTP previous to 4.14, when there is an error, it does not outputs any Object.
   Once the object Siteconfig is in ArgoCD, the only Error you will see is that Siteconfig is not a Known object.

This is hidden the root of the problem, something wrong in your Siteconfig, the plugin found the error, but it is hidden. So, it makes hard to debug, unless you use the plugin on your own.

Version-Release number of selected component (if applicable):

    4.14

How reproducible:

    Create a siteconfig, for exaple, with an extra-manifests folder that does not exists. This will cause a problem

Steps to Reproduce:

    1.Create a siteconfig, for exaple, with an extra-manifests folder that does not exists. This will cause a problem
    2. The error of the extra-manifest is hidden internally
    3. In ArgoCD is created a Siteconfig file
    4. You see an error because of the Siteconfig Kind dont exists. But you dont really see the real problem
    

Actual results:

    Siteconfig uploaded to ARgocd

Expected results:

    The plugin dont produces any output resource. In ArgoCD an error about siteconfig with an extra-manifest folder that does not exist.

Additional info: