spec
spec copied to clipboard
Open Application Model (OAM).
Hi all! Following the conversations from the last community call, this issue is a proposal to introduce a mechanism to be able to reference items of the application structure from...
To grow community support for OAM and ensure community involvement, the governance structure and membership needs to be updated. I suggest that there be a voting structure, organizations be given...
In real world application delivery, a rollout Trait may not simply represent a rollout capability, but more like a pipeline, i.e. it includes several stages with rollback, automatic canary analysis...
The first definition defined in the component schema looks to be incorrect. Currently, the `componentSpec` defines no JSON Schema keywords, and so emposes no constrains as to what it should...
Possible to update the OAM specifications to include reference to Distributed Application Runtime (DAPR)? How DAPR vis-a-vis to OAM.
Hi everyone, following the last community call, I am adding this issue to reflect an alternative point of view with regards to the presented [workflow proposal](https://github.com/oam-dev/kubevela/blob/master/design/vela-core/workflow_policy.md). The key elements that...
Following on the last community call items, the concept of having a catalog for OAM applications is an interesting topic that is being actively developed by some of the members....
(It's been mentioned during other discussions but I want to put up a separate proposal for it) # Overview Conceptually, ApplicationConfiguration serves for several purposes - it describes application topology,...
# OAM Spec v0.3.0 Working Draft Hi all, this is the issue tracker to finalize the design of OAM spec v0.3.0. It reflects the high level ideas of the existing...
As OAM matures, its complexity increases. As OAM is designed to separate operation concerns from developers, there’s a need to provide a developer-focused modeling language on top of the OAM...