Zheng Xi Zhou

> @wonderflow Note that for non-core workload it still need revision labels to be automatically patched (not propagation). Then let's automatically patch those labels including `component.oam.dev/name`. Users will be happy...

> Note that this proposal relies on: https://github.com/crossplane/oam-kubernetes-runtime/pull/175/files For ContainerizedWorkload, the labels of the workload can be propagated to deployments and pods, but for other non-core workloads, like deployment, the...

@erdun FYI, a related issue in oam-kubernetes-runtime https://github.com/crossplane/oam-kubernetes-runtime/issues/66

@zhangxiaoyu-zidif As OAM supports extended traits contributed by other developers, the whole trait list is hard to be complete, nor will it easy to fill items in the whitelist and...

@zhangxiaoyu-zidif Maybe the Trait catalog can help:) https://github.com/oam-dev/catalog/tree/master/traits

Hit the issue today. Any specification for pod/job dependencies definition?

@anoop2811 It makes sense. You can set it directly like the code sample. In the future, if we need to interact with Isitio, we can expose the setting of the...

@matt-mi Thanks for your interest in this project. Which could resources do you need?

> It would be better to have some commonly used resources supported like azure kubernetes service, azure functions, application gateways, web app service, azure sql and etc.. > Here is...

@Madhur97 Can you continue with this PR?