Files
kubevela/pkg/addon/testdata/example
Charlie Chiang 572fba3539 Fix: address failure when rendering addon API schemas (#4433)
* Fix: address failure when rendering addon API schemas

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>

* Fix: address failure when rendering addon API schemas

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>

* Test: add tests

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>

* Test: fix tests

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>

* Test: fix tests

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>
2022-07-25 17:00:57 +08:00
..
2021-12-01 19:15:48 +08:00

Example FluxCD Addon

This is an example addon based FluxCD

Directory Structure

  • template.yaml: contains the basic app, you can add some component and workflow to meet your requirements. Other files in resources/ and definitions/ will be rendered as Components and appended in spec.components
  • metadata.yaml: contains addon metadata information.
  • definitions/: contains the X-Definition yaml/cue files. These file will be rendered as KubeVela Component in template.yaml
  • resources/:
    • parameter.cue to expose parameters. It will be converted to JSON schema and rendered in UI forms.
    • All other files will be rendered as KubeVela Components. It can be one of the two types:
      • YAML file that contains only one resource. This will be rendered as a raw component
      • CUE template file that can read user input as parameter.XXX as defined parameter.cue. Basically the CUE template file will be combined with parameter.cue to render a resource. You can specify the type and trait in this format