Lei Zhang (Harry)
Lei Zhang (Harry)
My feeling is maybe we can still define core traits as reference but don't have to enforce runtime must implement them all.
/cc @vturecek @hongchaodeng @ryanzhang-oss @artursouza @wonderflow for review.
We should not assume Definition always has same name with `defitionRef`.
+1 to use label/selector instead of introducing new field.
@kminder Hi Kevin, just to confirm, you are suggesting using structured fields, or a specific object (e.g. WorkloadType) instead of labels to carry these characteristic (i.e. replicable) data, right? This...
@chilung Based on the discussion on gitter, I belive this is in scope of OAM and a valuable use case. I'd suggest we start from including this ApplicationScope from [extend...
@nathanawmk Dapr is not vis-a-vis to OAM. In nutshell, OAM can be used to deploy everything including Dapr powered app.
Thanks for reporting! My 2c is it may be way easier to generate from KubeVela's go types directly - it's where the constraints are enforced indeed.
@Relequestual Yeah, we already explored it a bit actually. For example, vela now [auto-generating json schema](https://kubevela.io/docs/platform-engineers/openapi-v3-json-schema) for the `schematic` section of OAM entities, and then build UI forms with it....
nits, It's OAM vs kubernetes-sigs/application, not SIG App.