Lei Zhang (Harry)

Yes! The `XXXDefinition` currently is designed as a mapping project to track upper level object to lower level object. For example, `ContainerizedWorkload` -> `Deployment`, or `RolloutTrait` -> `FlaggerRolloutTrait`. So in...

> First, having a Secret trait would be a great add-on from operational experience. Second, auto injection has nothing to do with Secret, but more about object definition mapping. This...

@allenhaozi Hi, it seems community is really interested in this feature, so we create a new issue to track it: #211 Feel free to comment/input there! Could you please close...

@BBialeckiACR I'm thinking maybe it's possible to define default values in TraitDefinition (as we already did in kubevela's implementation).

@BBialeckiACR The existing data input/output design in oam runtime seems closely related to your request, could you please take a look at this doc: https://github.com/crossplane/oam-kubernetes-runtime/blob/master/design/resource-dependency.md? It's already implemented in this...

@BBialeckiACR Per today's discussion, this is a valid use case and we should think how to support it. Would you mind to list the change needed in OAM spec in...

@BBialeckiACR As we discussed on the community meeting, the next step is to formalize the idea into a design proposal to change the spec. One example is: https://github.com/oam-dev/spec/pull/304 As long...

@wonderflow `appliesTo` and `conflictsWith` should follow the same pattern, one example is: ```yaml apiVersion: core.oam.dev/v1alpha2 kind: TraitDefinition metadata: name: virtualservices.networking.istio.io annotations: alias: traffic spec: appliesTo: - apps.k8s.io conflictsWith: - services.k8s.io...

@hongchaodeng one possible solution may be "mark" the selector filed path in definition object and let OAM runtime to inject required information (similar to a patch trait).

@ryanzhang-oss The second case is actually not a dependency issue, it's a discover issue. I'd propose OAM runtime automatically generate Services for a given component based on its revision history...