Files
kubevela/references/cli/test-data/addon/sample
Charlie Chiang d3454ec9d5 Feat: implement addon push command (#4261)
* Feat: implement addon push command

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

* Refactor: split functions

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

* Feat: add command usages

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

* Test: add tests for addon push command

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

* Chore: fix lint

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

* Test: fix old incomplete tests

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

* Test: also add test in pkg/addon

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

* Style: sort import

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

* Refactor: add break in for loop and remove default repo checks

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

* Style: format imports

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

* Feat: add a cli option to keep original Chart.yaml

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

* Style: add more help text

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

* Style: fix typo in comments

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

* Style: add more help text

Signed-off-by: Charlie Chiang <charlie_c_0129@outlook.com>
2022-06-28 20:16:45 +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