kubevela(2d958006182e489fd1139ba7d4b421fc83025034) for refs/heads/master commit

This commit is contained in:
kubevela-bot 2021-03-29 12:27:19 +00:00
parent 34e8aa78ab
commit d95675363b
2 changed files with 13 additions and 4 deletions

View File

@ -151,7 +151,6 @@ After the `Application` resource is applied to Kubernetes cluster, the KubeVela
|`app.oam.dev/name=<app name>` | The name of the application it belongs to |
|`app.oam.dev/component=<component name>` | The name of the component it belongs to |
|`trait.oam.dev/resource=<name of trait resource instance>` | The name of trait resource instance |
> TBD: the revision names and labels for resource instances are currently work in progress.
|`app.oam.dev/appRevision=<name of app revision>` | The name of the application revision it belongs to |
> TBD: a demo for kubectl apply above Application CR and show full detailed underlying resources.

View File

@ -175,7 +175,7 @@ spec:
KubeVela allows you to reference the runtime information of your application via `conext` keyword.
The most widely used context is application name(`context.appName`) and component name(`context.name`).
The most widely used context is application name(`context.appName`) component name(`context.name`).
```cue
context: {
@ -204,7 +204,17 @@ output: {
> Note that `context` information are auto-injected before resources are applied to target cluster.
> TBD: full available information in CUE `context`.
### Full available information in CUE `context`
| Context Variable | Description |
| :--: | :---------: |
| `context.appRevision` | The revision of the application |
| `context.appName` | The name of the application |
| `context.name` | The name of the component of the application |
| `context.namespace` | The namespace of the application |
| `context.output` | The rendered workload API resource of the component, this usually used in trait |
| `context.outputs.<resourceName>` | The rendered trait API resource of the component, this usually used in trait |
## Composition