spec
spec copied to clipboard
oam-dev
Open Application Model (OAM).
Consider "built-in" a set of essential patch traits in OAM Kubernetes platform (and hopefully works in all OAM platforms), regardless of what kind of encapsulation the component is using (Helm,...
We've mentioned this a bit in https://github.com/oam-dev/spec/issues/240 so just more details here. The _global trait_ is an operational capability which applies to multiple applications (AppConfig) rather than multiple components. The...
Consider adding operational hints (workload characteristic) on workload definition: ```yaml workload.oam.dev/exposed: true # exposes service endpoints workload.oam.dev/replicable: true # can be scale workload.oam.dev/daemonized: true # should be auto restart when...
Workload settings moving to the application configuration first makes the workload parameters irrelevant. Parameters were designed to allow component developers to make settings mutable or require user input, but not...
We are experiencing timing issues with the application of changes resulting from trait and scope processing to application resources. In particular we have an example of workload type of which...
[Issue 422 requests Entrypoints](https://github.com/oam-dev/spec/issues/422) to be added to the spec as a resource that can be defined. As these entrypoints will have security built around them the re is an...
Entrypoint - Entrypoints describe how data is accepted and results are emitted. Entrypoints and their security are defined as part of a Components Workload. For DICOM Use Case DimseInEntrypoint, DimseOutEntrypoint,...
Specifically state that traits apply to components and scopes apply globally to an application. Settings in traits and components are essentially parameters themselves, but trying to have components opt in...
We have found an issue related to the expectations of what happens with a component on an _ApplicationConfiguration_ entity. Launching the [containerized-workload](https://github.com/crossplane/oam-kubernetes-runtime/tree/master/examples/containerized-workload) example once, and then copying the _ApplicationConfiguration_, changing...
In the component example the port is listed with name and value attributes, but the spec is now name and containerPort. This needs to be fixed in the example.