Update componenttype examples to match current state

Author: ChathurangaKCD

docs/reference/api/application/component.md

@@ -5,9 +5,9 @@ title: Component API Reference
 # Component
 
 A Component represents a deployable unit of an application in OpenChoreo. It serves as the core abstraction that
-defines the component type (Service, WebApplication, ScheduledTask, etc.) and optionally includes build configuration
-when using OpenChoreo's CI system to build from source. Components are the primary building blocks used to define
-applications within a Project.
+references a platform-defined ComponentType (in `{workloadType}/{componentTypeName}` format) and optionally includes
+build configuration when using OpenChoreo's CI system to build from source. Components are the primary building blocks
+used to define applications within a Project.
 
 ## API Version
 
@@ -33,7 +33,7 @@ metadata:
 | Field   | Type                                          | Required | Default | Description                                                                                            |
 |---------|-----------------------------------------------|----------|---------|--------------------------------------------------------------------------------------------------------|
 | `owner` | [ComponentOwner](#componentowner)             | Yes      | -       | Ownership information linking the component to a project                                               |
-| `type`  | [ComponentType](#componenttype)               | Yes      | -       | Specifies the component type (Service, WebApplication, ScheduledTask, etc.)                            |
+| `componentType` | string | Yes      | -       | Component type in `{workloadType}/{componentTypeName}` format (e.g., `deployment/web-app`). See [ComponentType](#componenttype-reference). |
 | `build` | [BuildSpecInComponent](#buildspecincomponent) | No       | -       | Optional build configuration when using OpenChoreo CI to build from source (omit for pre-built images) |
 
 ### ComponentOwner
@@ -42,15 +42,11 @@ metadata:
 |---------------|--------|----------|---------|-------------------------------------------------------|
 | `projectName` | string | Yes      | -       | Name of the project that owns this component (min: 1) |
 
-### ComponentType
+### ComponentType Reference
 
-The component type determines how the component will be deployed and what resources it can create.
-
-| Value            | Description                         |
-|------------------|-------------------------------------|
-| `Service`        | Long-running service component      |
-| `WebApplication` | Web application with HTTP endpoints |
-| `ScheduledTask`  | Scheduled/cron job component        |
+The `componentType` string points to a platform-defined ComponentType using the format `{workloadType}/{componentTypeName}`.
+Examples: `deployment/service`, `cronjob/scheduled-task`, `deployment/web-application`. See [ComponentType](../platform/componenttype.md)
+for details.
 
 ### BuildSpecInComponent
 
@@ -115,7 +111,7 @@ metadata:
 spec:
   owner:
     projectName: my-project
-  type: Service
+  componentType: deployment/service
   build:
     repository:
       url: https://github.com/myorg/customer-service
@@ -142,7 +138,7 @@ metadata:
 spec:
   owner:
     projectName: my-project
-  type: WebApplication
+  componentType: deployment/web-app
   build:
     repository:
       url: https://github.com/myorg/frontend

docs/reference/api/platform/componenttype.md

@@ -53,10 +53,10 @@ Defines the configurable parameters that developers can set when creating compon
 
 #### Parameter Schema Syntax
 
-Parameters use inline schema syntax with pipe-separated modifiers:
+Parameters use inline schema syntax with a single pipe after the type; constraints are space-separated:
 
 ```
-fieldName: "type | default=value | required=true | enum=val1,val2"
+fieldName: "type | default=value enum=val1,val2"
 ```
 
 Supported types: `string`, `integer`, `boolean`, `array<type>`, custom type references
@@ -203,7 +203,7 @@ spec:
 
   schema:
     parameters:
-      schedule: "string | required=true"
+      schedule: string
       concurrencyPolicy: "string | default=Forbid | enum=Allow,Forbid,Replace"
 
   resources:

docs/reference/api/platform/trait.md

@@ -47,19 +47,19 @@ Defines the configurable parameters that developers can set when attaching this
 
 #### Parameter Schema Syntax
 
-Uses the same inline schema syntax as ComponentType:
+Uses the same inline schema syntax as ComponentType: a single pipe after the type, then space-separated constraints:
 
 ```
-fieldName: "type | default=value | required=true | enum=val1,val2"
+fieldName: "type | default=value enum=val1,val2"
 ```
 
 **Example:**
 
 ```yaml
 schema:
   parameters:
-    volumeName: "string | required=true"
-    mountPath: "string | required=true"
+    volumeName: string
+    mountPath: string
     containerName: "string | default=app"
 
   envOverrides:
@@ -110,7 +110,7 @@ Defines a modification using JSONPatch format (RFC 6902) with OpenChoreo extensi
 
 | Field   | Type   | Required | Description                                           |
 |---------|--------|----------|-------------------------------------------------------|
-| `op`    | string | Yes      | Operation: `add`, `replace`, `remove`, `mergeShallow` |
+| `op`    | string | Yes      | Operation: `add`, `replace`, `remove` |
 | `path`  | string | Yes      | JSON Pointer to the field (RFC 6901)                  |
 | `value` | any    | No       | Value to set (not used for `remove`)                  |
 
@@ -119,14 +119,13 @@ Defines a modification using JSONPatch format (RFC 6902) with OpenChoreo extensi
 - **add**: Add a new field or array element
 - **replace**: Replace an existing field value
 - **remove**: Delete a field
-- **mergeShallow**: OpenChoreo extension for overlaying map keys
 
 #### Path Syntax
 
 Supports array filters for targeting specific elements:
 
 ```
-/spec/containers/[?(@.name=='app')]/volumeMounts/-
+/spec/containers[?(@.name=='app')]/volumeMounts/-
 ```
 
 ## Examples
@@ -142,8 +141,8 @@ metadata:
 spec:
   schema:
     parameters:
-      volumeName: "string | required=true"
-      mountPath: "string | required=true"
+      volumeName: string
+      mountPath: string
       containerName: "string | default=app"
 
     envOverrides:
@@ -172,7 +171,7 @@ spec:
         kind: Deployment
       operations:
         - op: add
-          path: /spec/template/spec/containers/[?(@.name=='${trait.parameters.containerName}')]/volumeMounts/-
+          path: /spec/template/spec/containers[?(@.name=='${trait.parameters.containerName}')]/volumeMounts/-
           value:
             name: ${trait.parameters.volumeName}
             mountPath: ${trait.parameters.mountPath}
@@ -239,12 +238,12 @@ spec:
         version: v1
         kind: Deployment
       operations:
-        - op: mergeShallow
-          path: /spec/template/spec/containers/[?(@.name=='main')]/resources
-          value:
-            limits:
-              cpu: ${trait.parameters.cpuLimit}
-              memory: ${trait.parameters.memoryLimit}
+        - op: add
+          path: /spec/template/spec/containers[?(@.name=='main')]/resources/limits/cpu
+          value: ${trait.parameters.cpuLimit}
+        - op: add
+          path: /spec/template/spec/containers[?(@.name=='main')]/resources/limits/memory
+          value: ${trait.parameters.memoryLimit}
 ```
 
 ### Multi-Container Trait with forEach
@@ -257,8 +256,12 @@ metadata:
   namespace: default
 spec:
   schema:
+    types:
+      Mount:
+        name: string
+        path: string
     parameters:
-      mounts: "array<object> | required=true"
+      mounts: "[]Mount"
 
   patches:
     - target:
@@ -274,7 +277,7 @@ spec:
             name: ${mount.name}
             emptyDir: {}
         - op: add
-          path: /spec/template/spec/containers/[?(@.name=='app')]/volumeMounts/-
+          path: /spec/template/spec/containers[?(@.name=='app')]/volumeMounts/-
           value:
             name: ${mount.name}
             mountPath: ${mount.path}