Argo Workflows Io K8S Api Core V1 Config Map Projection Structure

{
  "$schema": "https://json-structure.org/meta/core/v0/#",
  "$id": "https://raw.githubusercontent.com/api-evangelist/argo-workflows/refs/heads/main/json-structure/argo-workflows-io-k8s-api-core-v1-config-map-projection-structure.json",
  "name": "io.k8s.api.core.v1.ConfigMapProjection",
  "description": "Adapts a ConfigMap into a projected volume.\n\nThe contents of the target ConfigMap's Data field will be presented in a projected volume as files using the keys in the Data field as the file names, unless the items element is populated with specific mappings of keys to paths. Note that this is identical to a configmap volume source without the default mode.",
  "type": "object",
  "properties": {
    "items": {
      "description": "items if unspecified, each key-value pair in the Data field of the referenced ConfigMap will be projected into the volume as a file whose name is the key and content is the value. If specified, the listed keys will be projected into the specified paths, and unlisted keys will not be present. If a key is specified which is not present in the ConfigMap, the volume setup will error unless it is marked optional. Paths must be relative and may not contain the '..' path or start with '..'.",
      "type": "array",
      "items": {
        "$ref": "#/definitions/io.k8s.api.core.v1.KeyToPath"
      },
      "x-kubernetes-list-type": "atomic"
    },
    "name": {
      "description": "Name of the referent. This field is effectively required, but due to backwards compatibility is allowed to be empty. Instances of this type with an empty value here are almost certainly wrong. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names",
      "type": "string"
    },
    "optional": {
      "description": "optional specify whether the ConfigMap or its keys must be defined",
      "type": "boolean"
    }
  }
}