kubevela/vela-templates/definitions
曾子恒 f46bfcf131
Fix(CUE): fix variable error bug in startup-probe (#6472)
The original variable is "grtcpSocketpc", but this variable does not
exist in the file. According to the context, it should be "tcpSocket".
In addition, its type needs to be int to work properly.

Signed-off-by: zengziheng <zengziheng@datacloak.com>
Co-authored-by: zengziheng <zengziheng@datacloak.com>
2024-04-07 10:38:33 +08:00
..
deprecated Feat: add category for workflow step definition (#5471) 2023-02-10 14:23:04 +08:00
internal Fix(CUE): fix variable error bug in startup-probe (#6472) 2024-04-07 10:38:33 +08:00
registry Chore: remove legacy rollout and scope (#6068) 2023-06-05 10:57:38 +08:00
usage-examples Fix: parameter type is conflict with Component webserice and Trait re… (#5579) 2023-03-15 20:36:00 +08:00
README.md [Vela CLI] Vela def enhancement & replace mergedef.sh (#2031) 2021-08-06 17:10:52 +08:00

README.md

Vela Definitions

This directory contains KubeVela definitions that could be used in Applications to extend the ability of workloads.

To install definition like internal/resource.cue, run vela def apply internal/resource.cue to install it. You can check if by running vela def get resource or vela def list. Optionally, you can run vela up -f ./usage-examples/application-with-resource.yaml to see how to use this resource definition with an application.

If you would like to customize your own resource definitions, you can run vela def edit resource or edit the internal/resource.cue file locally and then re-run vela def apply internal/resource.cue. You can also run vela def vet internal/resource.cue to check if your modification is valid.

If you do not want it anymore, you can run vela def del resource to remove it.

Finally, if you would like to create your own definition from scratch, you can run vela def init my-definition -i to initiate your definition.