spec
spec copied to clipboard
oam-dev
Open Application Model (OAM).
Our Traits are loosely coupled which means a user or platform builder can easily add a trait for some kinds of workload. But we can't recognize whether a new trait...
There are many users who rely on Terraform or similar tooling (ARM, ROS) to deploy infrastructure resources on cloud, e.g. EC2, RDS, k8s cluster. After deploying infra resources, users want...
In the current OAM spec (v0.2.1) scopes supported as an attribute of component. I believe that the most common use case for a scope will be to apply the scope...
It has been proved that childResource is a strong need for any abstraction workload (e.g. ContainerizedWorkload), so that Trait controller could know what's the underlying workload object it need to...
Per [the spec](https://github.com/oam-dev/spec/blob/v0.2.1/3.workload.md#categories-of-workload): > OAM implementations MUST implement all core workloads as defined in this specification. And then further down, we see the list of core workloads in the specification:...
As we discussed before, trait is something like properties, so one kind of trait should only bind to component once. But recently more and more demands come up that we...
[Dependency management feature](https://github.com/crossplane/oam-kubernetes-runtime/blob/master/design/resource-dependency.md) has been implementedin [oam-k8s-runtime](https://github.com/crossplane/oam-kubernetes-runtime/tree/master/examples/dependency). We should add it back into spec.
**Is the content in the red box filled by developers or operators?**   
Doc standard labels, data input/output (experimental) and revisioning in the spec.
Suppose an edge service in Bay Area serve me well and then I fly to New York, another edge service serve me well too. However, the edge service in New...
