Managing KubeVela Addons with Duplicate Names

[Jayashree138]

Hey,
While working on a KubeVela addon, I've noticed a curious behavior where multiple addons with the same name are generated with respect to the number of files in resource folder containing Application YAML files. When I execute the vela addon disable command, all these duplicate copies are removed. I'm curious to understand why this happens and what it means for managing KubeVela addons.

[Jayashree138]

example:

resource file :

[chivalryq]

Can you show the content of application YAML?

[chivalryq]

And what's the use case for putting application in resources?

[Jayashree138]

Use Case: We have 2 addons where in first addon creates the definitions and the second addon is used to deploy the application files. The application files are kept in the resource folder as it only applies once when the addon is created. The two addons have dependencies specified in order to have the right workflow.

[chivalryq]

I see, but can you check the application's name in resources?

[Jayashree138]

The application names are different:

application example:

apiVersion: core.oam.dev/v1beta1
kind: Application
metadata:
  name: application1
spec:
  components:
    - name: app1
    -type: cluster-resource-1 # CRD from addon 1

One more clarity: 
Addon 1: Creates CRDs (definition)
Addon 2: Creates application with type created by addon1.

[chivalryq]

If the application name differs and after enabling addon there are three addon listed with the same name (test-addon), there might be a bug in vela addon list or vela addon enable. You can check if the application name in cluster is as expected. There should be two apps: addon-test and application1