Parent devworkspace template
| Name | Type | Description | Notes |
|---|---|---|---|
| attributes | Object | Overrides of attributes encapsulated in a parent devfile. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| commands | List<V1alpha2DevWorkspaceSpecTemplateParentCommands> | Overrides of commands encapsulated in a parent devfile or a plugin. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| components | List<V1alpha2DevWorkspaceSpecTemplateParentComponents> | Overrides of components encapsulated in a parent devfile or a plugin. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| id | String | Id in a registry that contains a Devfile yaml file | [optional] |
| kubernetes | V1alpha2DevWorkspaceSpecTemplateParentKubernetes | [optional] | |
| projects | List<V1alpha2DevWorkspaceSpecTemplateParentProjects> | Overrides of projects encapsulated in a parent devfile. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| registryUrl | String | Registry URL to pull the parent devfile from when using id in the parent reference. To ensure the parent devfile gets resolved consistently in different environments, it is recommended to always specify the `registryUrl` when `id` is used. | [optional] |
| starterProjects | List<V1alpha2DevWorkspaceSpecTemplateParentStarterProjects> | Overrides of starterProjects encapsulated in a parent devfile. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| uri | String | URI Reference of a parent devfile YAML file. It can be a full URL or a relative URI with the current devfile as the base URI. | [optional] |
| variables | Map<String, String> | Overrides of variables encapsulated in a parent devfile. Overriding is done according to K8S strategic merge patch standard rules. | [optional] |
| version | String | Specific stack/sample version to pull the parent devfile from, when using id in the parent reference. To specify `version`, `id` must be defined and used as the import reference source. `version` can be either a specific stack version, or `latest`. If no `version` specified, default version will be used. | [optional] |