Referring to a parent devfile in a devfile
This section describes how to designate a parent devfile to a given devfile. If you designate a parent devfile, the given devfile inherits all its behavior from its parent. Still, you can use the child devfile to override certain content from the parent devfile. If you override the correct content, you can reuse the same parent devfile in multiple other devfiles. If you do reuse a parent devfile, the parent turns into a stack that is used in multiple other devfiles.
You can refer to a parent devfile in three different ways:
kubernetesExample 1. Parent referred by registry
idwhen published in a registry. Provide the
registryUrlas well as
versioncan be either the stack version string, or
latest. If no
versionis provided, the default version for the stack will be used.
schemaVersion: 2.2.0 metadata: name: my-project-dev parent: id: redhat/nodejs registryUrl: https://devfile-registry.io/ version: 1.2.0Example 2. Parent referred by URI
Using the URI when published on a static HTTP server, such as GitHub Gist or Pastebin.
schemaVersion: 2.2.0 metadata: name: my-project-dev parent: uri: https://raw.githubusercontent.com/devfile/registry/main/stacks/nodejs/devfile.yamlExample 3. Parent identified by a Kubernetes resource
Using a Kubernetes resource name and namespace if it has been deployed on a Kubernete cluster.
schemaVersion: 2.2.0 metadata: name: my-project-dev parent: kubernetes: name: mydevworkspacetemplate namespace: mynamespace
For more information about referring to parent devfiles, see: