You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When attempting to generate manifests using the KCL plugin, I encounter the following error: "failed to unmarshal manifest: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context." This error persists until I perform a hard refresh, despite making no changes to the codebase.
To Reproduce
Steps to reproduce the behavior:
Deploy an application using ArgoCD with the KCL plugin.
Observe the error in the ArgoCD UI or through CLI output.
Note that the error appears consistently until a hard refresh is performed.
Expected behavior
Manifest generation should occur without errors, without the need for hard refreshes to correct YAML to JSON conversion issues.
Version
ArgoCD Version: 6.9.1
Logs
generating manifests: failed to unmarshal manifest: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context
Additional context
The issue occurs consistently under the current setup, using the KCL plugin, and without any recent changes to the YAML files or configurations that might explain this behavior.
The text was updated successfully, but these errors were encountered:
Describe the bug
When attempting to generate manifests using the KCL plugin, I encounter the following error: "failed to unmarshal manifest: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context." This error persists until I perform a hard refresh, despite making no changes to the codebase.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Manifest generation should occur without errors, without the need for hard refreshes to correct YAML to JSON conversion issues.
Version
Logs
generating manifests: failed to unmarshal manifest: error converting YAML to JSON: yaml: line 2: mapping values are not allowed in this context
Additional context
The issue occurs consistently under the current setup, using the KCL plugin, and without any recent changes to the YAML files or configurations that might explain this behavior.
The text was updated successfully, but these errors were encountered: