commit db4e4d282bd54fb6abf7f833b7e34646de54ce38
author Marcel van Lohuizen <mpvl@golang.org> Thu Apr 18 08:43:57 2019 +0200
committer Marcel van Lohuizen <mpvl@google.com> Thu Apr 18 08:39:03 2019 +0000
tree cd36f1ad6c85962b017010b13320bb8b2647f2a6
parent 433ab7a9079af5410fa6d5270016fce533891799

doc/tutorial/kubernetes

Update Kubernetes tutorial.

Fixes #31.

Change-Id: Ie6515dcdb61cc0aab59f20097f8e68317bc07d28
Reviewed-on: https://cue-review.googlesource.com/c/cue/+/1842
Reviewed-by: Marcel van Lohuizen <mpvl@google.com>

doc/tutorial/kubernetes/README.md

diff --git a/doc/tutorial/kubernetes/README.md b/doc/tutorial/kubernetes/README.md
index b59e4c5..cdddc23 100644
--- a/doc/tutorial/kubernetes/README.md
+++ b/doc/tutorial/kubernetes/README.md
@@ -224,9 +224,11 @@
 can verify that simplifications yield the same results.
 
 ```
-$ cue eval ./... > snapshot
+$ cue eval -c ./... > snapshot
 ```
 
+The `-c` option tells `cue` that only concrete values, that is valid JSON,
+are allowed.
 We focus on the objects defined in the various `kube.cue` files.
 A quick inspection reveals that many of the Deployments and Services share
 common structure.
@@ -272,7 +274,7 @@
     metadata name: Name
     spec: {
         // 1 is the default, but we allow any number
-        replicas: 1 | int
+        replicas: *1 | int
         template: {
             metadata labels: {
                 app:       Name
@@ -322,7 +324,7 @@
 Let's compare the result of merging our new template to our original snapshot.
 
 ```
-$ cue eval ./... > snapshot2
+$ cue eval ./... -c > snapshot2
 --- ./mon/alertmanager
 non-concrete value (string)*:
     ./kube.cue:11:15
@@ -369,7 +371,7 @@
 Let's try again to see if it is fixed:
 
 ```
-$ cue eval ./... > snapshot2
+$ cue eval -c ./... > snapshot2
 $ diff snapshot snapshot2
 ...
 ```