Lei Zhang (Harry)

I deep dived[ Terraform examples ](https://github.com/hashicorp/terraform/tree/master/examples)for a bit, here's a draft plan: 1. A generic controller impl, i.e.: https://github.com/spotahome/gontroller; 1. or we just install the controller in a minimized K8s...

@ghostbody Implementing OAM without k8s is even simpler because you don't need to care about controller pattern at all. Just translate the OAM yamls into Terraform or CloudFormation files is...

@ghostbody Yes, your understanding about IaD vs IaC is correct. So the approaches available to make Terraform K8s native are: 1. Crossplane with Terraform as provider: https://github.com/crossplane/crossplane/pull/1677/files 2. Use Terraform...

Option 2 seems practical to me.

@technosophos For non-K8s implementation in our side, a common use case is accounting cloud resources referenced by this application. I think this obj could be a useful & generic spec...

I will re-open this issue since the community is now actively working on the `appfile` (ref: https://github.com/oam-dev/spec/issues/389), which is exactly originated from this proposal. /cc @Haishi2016 It will need to...

Hi @kminder, Appfile is designed as a **client side** abstraction to simplify user input and render OAM objects. But we are also discussing if need to move its implementation to...

@kminder Another detail I'd like to reference is: https://github.com/oam-dev/kubevela/issues/399#issuecomment-711064876. As the tool/modeling language for developers, Appfile will include features in its upcoming releases such as `build` and `release`. They are...

We also need to define **category of traits** as we already did internal Alibaba. A labelSelector style solution seems good. I will still suggest consider OPA as the policy engine...

@negz @hasheddan Though open for discussion, I personally think the quick answer for core workload/trait/scope is: NO - newly added fields should be introduced into the spec, and I'd suggest...