* Feat: expose HTTP timeout on built-in workflow steps Allow request, webhook, and notification steps to set an optional timeout (Go duration string) that is forwarded to http.#HTTPDo as request.timeout, so slow HTTP calls are no longer stuck at the 3s default. Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com> * Feat: Made requested changes Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com> * Fix: align timeout duration regex with Go ParseDuration Accept "0" and leading-dot fractions like ".5s", matching time.ParseDuration more closely while still rejecting unit-less values such as "30". Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com> --------- Signed-off-by: shaurya2k06 <shaurya2k06@gmail.com>
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.