Reference newer 2.1.0 schemaVersion in samples

Author: sleshchenko

docs/modules/user-guide/partials/proc_adding-a-name-to-a-devfile.adoc

@@ -16,7 +16,7 @@ Adding a name to a devfile is mandatory. Both `name` and `generateName` are opti
 
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: devfile-sample
   version: 2.0.0
@@ -28,7 +28,7 @@ metadata:
 
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: devfile-sample
   version: 2.0.0

docs/modules/user-guide/partials/proc_adding-attributes-to-a-devfile.adoc

@@ -21,7 +21,7 @@ When no editor is specified, a default editor is provided. To represent this use
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: petclinic-dev-environment
   attributes:

docs/modules/user-guide/partials/proc_adding-commands-to-a-devfile.adoc

@@ -37,7 +37,7 @@ A devfile allows to specify commands to be available for execution in a workspac
 +
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 projects:
@@ -76,7 +76,7 @@ A given command can be assigned to one or more groups that represents the nature
 +
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 projects:
@@ -113,7 +113,7 @@ A composite command can be defined to chain multiple commands together. The indi
 +
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 projects:

docs/modules/user-guide/partials/proc_adding-container-component-to-a-devfile.adoc

@@ -41,7 +41,7 @@ A component type that allows to define a container image-based configuration of
 .A minimal `container` component*
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
     name: mydevfile
 components:
@@ -62,7 +62,7 @@ For the `container` component to have access to the project sources, you must se
 +
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
     name: mydevfile
 components:

docs/modules/user-guide/partials/proc_adding-projects-to-a-devfile.adoc

@@ -20,7 +20,7 @@ This section describes how to add one or more projects to a devfile.
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: petclinic-dev-environment
   version: 2.0.0
@@ -38,7 +38,7 @@ projects:
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: example-devfile
   version: 2.0.0
@@ -95,7 +95,7 @@ source:
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: my-project-dev
   version: 2.0.0

docs/modules/user-guide/partials/proc_adding-schema-version-to-a-devfile.adoc

@@ -13,12 +13,12 @@ The `schemaVersion` attribute is mandatory in a devfile.
 ====
 [source,yaml]
 ----
-v2.0
+v2.1
 ---
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: devfile-sample
-  version: 2.0.0
+  version: 2.1.0
 ----
 ====
 

docs/modules/user-guide/partials/proc_defining-endpoints.adoc

@@ -12,7 +12,7 @@ Components of any type can specify the endpoints that the container exposes. The
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 projects:
@@ -73,7 +73,7 @@ When starting a new server within a component, {prod-short} autodetects this, an
 
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 components:

docs/modules/user-guide/partials/proc_defining-environment-variables.adoc

@@ -13,7 +13,7 @@ If the component has multiple containers, environment variables will be provisio
 ====
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 components:

docs/modules/user-guide/partials/proc_defining-kubernetes-resources.adoc

@@ -19,7 +19,7 @@ Complex deployments can be described using Kubernetes or OpenShift resource list
 
 [source,yaml]
 ----
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: mydevfile
 projects:

docs/modules/user-guide/partials/proc_migrating-schema-version.adoc

@@ -6,7 +6,7 @@ This section describes how to migrate the existing schema version to a v2.x devf
 
 .Procedure
 
-. To migrate a schema version from a v1.x devfile to a v2.x devfile, replace `apiVersion: 1.0.0` with `schemaVersion: 2.0.0`:
+. To migrate a schema version from a v1.x devfile to a v2.x devfile, replace `apiVersion: 1.0.0` with `schemaVersion: 2.1.0`:
 +
 [cols="1a,1a"]
 |====
@@ -24,7 +24,7 @@ metadata:
 ----
 v2.0
 ---
-schemaVersion: 2.0.0
+schemaVersion: 2.1.0
 metadata:
   name: devfile-sample
 ----