Daniel Higuero

Thanks @charlie0129, @Somefive for the extra information. I was not aware of the current parametrization capabilities for addons. With this I think the first problem of being able to pass...

Hi @wonderflow, I will to try rephrase the issue. The main problem I see with the current approach if we do not add any consistency mechanism is that by adding...

I think that for a `multitenant` installation only admins should be able to install addons as creating cluster-wide entities and/or operators will be restricted.

I think that will work from the point of view of Kubevela core. From the point of view of the addon developer, i think we should make this type of...

Hi all, for me it is still a bit confusing, so I think we should try clarify what will be the use cases for both the current `Application.spec.workflow` and the...

Thanks for the updated proposal, i will try to answer some the previous questions first, > IMO, the WorkflowRun that is generated from an Application should have some ownerReference that...

I agree with the proposal to better reference the parent/associated application with a WorkflowRun. However, I still have some doubts about the overall lifecycle and triggers. I think that some...

Thanks @FogDong for the feedback, I will try to answer the different questions: Q1: The first idea that comes to mind would be a use case where we are using...

Thanks @wonderflow for the ping-back. To give some context, when this was discussed in the OAM spec, AFAIK the main use case was the ability to store component definitions in...

Hi all, these are our comments on the spec proposal. ## Component Definition * Only one resource apiVersion/Kind is associated with a component. What if it generates multiple ones? *...