-
Notifications
You must be signed in to change notification settings - Fork 858
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Input validation for Kubevela Application manifests #6505
Comments
bugbounce
pushed a commit
to bugbounce/kubevela
that referenced
this issue
May 28, 2024
This also upgrades the version of cuelang to v0.6.0, which adds support for fields with "RequiredConstraint". The target for this commit is to validate if a required fields is missing from the input parameters and return a meaningful error useful w.r.t to the Kubevela Application. kubevela#6505
4 tasks
bugbounce
pushed a commit
to bugbounce/kubevela
that referenced
this issue
May 29, 2024
This also upgrades the version of cuelang to v0.6.0, which adds support for fields with "RequiredConstraint". The target for this commit is to validate if a required fields is missing from the input parameters and return a meaningful error useful w.r.t to the Kubevela Application. kubevela#6505 Signed-off-by: Rahul Kumar <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Currently Kubevela doesn't seem to have a mechanism to validate input fields in an Application before applying the manifest. Currently, the Application manifest deployment fails with an error with the workload output. This makes it difficult to debug, especially for end users.
To Reproduce
Steps to reproduce the behavior:
properties.name
missing.run step(provider=oam,do=component-apply): GenerateComponentManifest: evaluate base template component=myapptable app=test-kubevela-dynamodb-required: failed to have the workload/trait unstructured: output.metadata.name: non-concrete value string in operand to + (and 1 more errors)
Expected behavior
We expect a relevant error from the point of view of the end user defining the Application. The current form of the error cannot be interpreted by the end user. Kubevela should validate the Application manifest before applying and return any errors.
KubeVela Version
Vela Core : 1.9.10
Cluster information
Additional context
0.6.0
. https://github.com/cue-lang/cue/releases/tag/v0.6.0The text was updated successfully, but these errors were encountered: