|
1944 | 1944 | }, |
1945 | 1945 | "alwaysResolve": { |
1946 | 1946 | "type": "boolean", |
1947 | | - "description": "AlwaysResolve makes sure this variable will always be resolved and not only if it is used somewhere" |
| 1947 | + "description": "AlwaysResolve makes sure this variable will always be resolved and not only if it is used somewhere. Defaults to true." |
1948 | 1948 | }, |
1949 | 1949 | "source": { |
1950 | 1950 | "type": "string", |
|
2008 | 2008 | "description": "Functions are POSIX functions that can be used within pipelines. Those functions can also be imported by\nimports." |
2009 | 2009 | }, |
2010 | 2010 | "pipelines": { |
2011 | | - "oneOf": [ |
| 2011 | + "anyOf": [ |
2012 | 2012 | { |
2013 | | - "additionalProperties": { |
2014 | | - "type": "string" |
2015 | | - }, |
2016 | 2013 | "type": "object" |
2017 | 2014 | }, |
2018 | 2015 | { |
|
2023 | 2020 | "description": "Pipelines are the work blocks that DevSpace should execute when devspace dev, devspace build, devspace deploy or devspace purge\nis called. Pipelines are defined through a special POSIX script that allows you to use special commands\nsuch as create_deployments, start_dev, build_images etc. to signal DevSpace you want to execute\na specific functionality. The pipelines dev, build, deploy and purge are special and will override\nthe default functionality of the respective command if defined. All other pipelines can be either run\nvia the devspace run-pipeline command or used within another pipeline through run_pipelines." |
2024 | 2021 | }, |
2025 | 2022 | "images": { |
2026 | | - "patternProperties": { |
2027 | | - ".*": { |
2028 | | - "$ref": "#/definitions/Config/$defs/Image" |
| 2023 | + "anyOf": [ |
| 2024 | + { |
| 2025 | + "type": "object" |
| 2026 | + }, |
| 2027 | + { |
| 2028 | + "type": "object" |
2029 | 2029 | } |
2030 | | - }, |
| 2030 | + ], |
2031 | 2031 | "type": "object", |
2032 | 2032 | "description": "Images holds configuration of how DevSpace should build images. By default, DevSpace will build all defined images.\nIf you are using a custom pipeline, you can dynamically define which image is built at which time during the\nexecution." |
2033 | 2033 | }, |
2034 | 2034 | "deployments": { |
2035 | | - "patternProperties": { |
2036 | | - ".*": { |
2037 | | - "$ref": "#/definitions/Config/$defs/DeploymentConfig" |
| 2035 | + "anyOf": [ |
| 2036 | + { |
| 2037 | + "type": "object" |
| 2038 | + }, |
| 2039 | + { |
| 2040 | + "type": "object" |
2038 | 2041 | } |
2039 | | - }, |
| 2042 | + ], |
2040 | 2043 | "type": "object", |
2041 | 2044 | "description": "Deployments holds configuration of how DevSpace should deploy resources to Kubernetes. By default, DevSpace will deploy all defined deployments.\nIf you are using a custom pipeline, you can dynamically define which deployment is deployed at which time during the\nexecution." |
2042 | 2045 | }, |
|
2050 | 2053 | "description": "Dev holds development configuration. Each dev configuration targets a single pod and enables certain dev services on that pod\nor even rewrites it if certain changes are requested, such as adding an environment variable or changing the entrypoint.\nDev allows you to:\n- sync local folders to the Kubernetes pod\n- port forward remote ports to your local computer\n- forward local ports into the Kubernetes pod\n- configure an ssh tunnel to the Kubernetes pod\n- proxy local commands to the container\n- restart the container on file changes" |
2051 | 2054 | }, |
2052 | 2055 | "vars": { |
2053 | | - "oneOf": [ |
| 2056 | + "anyOf": [ |
2054 | 2057 | { |
2055 | | - "additionalProperties": { |
2056 | | - "type": "string" |
2057 | | - }, |
2058 | 2058 | "type": "object" |
2059 | 2059 | }, |
2060 | 2060 | { |
|
2065 | 2065 | "description": "Vars are config variables that can be used inside other config sections to replace certain values dynamically" |
2066 | 2066 | }, |
2067 | 2067 | "commands": { |
2068 | | - "oneOf": [ |
| 2068 | + "anyOf": [ |
2069 | 2069 | { |
2070 | | - "additionalProperties": { |
2071 | | - "type": "string" |
2072 | | - }, |
2073 | 2070 | "type": "object" |
2074 | 2071 | }, |
2075 | 2072 | { |
|
2080 | 2077 | "description": "Commands are custom commands that can be executed via 'devspace run COMMAND'. These commands are run within a pseudo bash\nthat also allows executing special commands such as run_watch or is_equal." |
2081 | 2078 | }, |
2082 | 2079 | "dependencies": { |
2083 | | - "patternProperties": { |
2084 | | - ".*": { |
2085 | | - "$ref": "#/definitions/Config/$defs/DependencyConfig" |
| 2080 | + "anyOf": [ |
| 2081 | + { |
| 2082 | + "type": "object" |
| 2083 | + }, |
| 2084 | + { |
| 2085 | + "type": "object" |
2086 | 2086 | } |
2087 | | - }, |
| 2087 | + ], |
2088 | 2088 | "type": "object", |
2089 | 2089 | "description": "Dependencies are sub devspace projects that lie in a local folder or remote git repository that can be executed\nfrom within the pipeline. In contrast to imports, these projects pose as separate fully functional DevSpace projects\nthat typically lie including source code in a different folder and can be used to compose a full microservice\napplication that will be deployed by DevSpace. Each dependency name can only be used once and if you want to use\nthe same project multiple times, make sure to use a different name for each of those instances." |
2090 | 2090 | }, |
2091 | 2091 | "pullSecrets": { |
2092 | | - "patternProperties": { |
2093 | | - ".*": { |
2094 | | - "$ref": "#/definitions/Config/$defs/PullSecretConfig" |
| 2092 | + "anyOf": [ |
| 2093 | + { |
| 2094 | + "type": "object" |
| 2095 | + }, |
| 2096 | + { |
| 2097 | + "type": "object" |
2095 | 2098 | } |
2096 | | - }, |
| 2099 | + ], |
2097 | 2100 | "type": "object", |
2098 | 2101 | "description": "PullSecrets are image pull secrets that will be created by devspace in the target namespace\nduring devspace dev or devspace deploy. DevSpace will merge all defined pull secrets into a single\none or the one specified." |
2099 | 2102 | }, |
|
0 commit comments