Skip to content

Commit a29968d

Browse files
Rename files.
1 parent ee5c936 commit a29968d

File tree

3 files changed

+9
-9
lines changed

3 files changed

+9
-9
lines changed

exercises/resources-v4/secret-3.yaml renamed to exercises/resources-v4/secret-3a.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
apiVersion: v1
88
kind: Secret
99
metadata:
10-
name: mysecret-3
10+
name: mysecret-3a
1111
type: Opaque
1212
stringData:
1313
password-1: #@ data.values.password1 if data.values.password1 != None else password(state)
File renamed without changes.

workshop/content/exercises/09-overriding-values.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ relied on as the only solution. When using generated values it is always going
44
to be good practice to allow them to be overridden through the data input
55
values when running ``ytt``.
66

7-
For how this can be done check out ``resources-v4/secret-3.yaml``.
7+
For how this can be done check out ``resources-v4/secret-3a.yaml``.
88

99
```editor:open-file
10-
file: ~/exercises/resources-v4/secret-3.yaml
10+
file: ~/exercises/resources-v4/secret-3a.yaml
1111
```
1212

1313
You can see how it will check for the password being defined as a data input
@@ -16,7 +16,7 @@ value and if it is use that, but otherwise generate a password.
1616
Running ``ytt`` on this:
1717

1818
```terminal:execute
19-
command: ytt -f resources-v4/random.star -f resources-v4/secret-3.yaml -f resources-v4/values.yaml
19+
command: ytt -f resources-v4/random.star -f resources-v4/secret-3a.yaml -f resources-v4/values.yaml
2020
```
2121

2222
we get:
@@ -35,7 +35,7 @@ stringData:
3535
Now override the password using a data input value:
3636

3737
```terminal:execute
38-
command: ytt -f resources-v4/random.star -f resources-v4/secret-3.yaml -f resources-v4/values.yaml -v password1=top-secret
38+
command: ytt -f resources-v4/random.star -f resources-v4/secret-3a.yaml -f resources-v4/values.yaml -v password1=top-secret
3939
```
4040

4141
which should yield:
@@ -64,16 +64,16 @@ To remedy this problem we need to ensure that we still always generate
6464
every password and only after we do this override it with a supplied value.
6565
This ensures everything else stays the same.
6666

67-
This version can been see in ``resources-v4/secret-4.yaml``.
67+
This version can been see in ``resources-v4/secret-3b.yaml``.
6868

6969
```editor:open-file
70-
file: ~/exercises/resources-v4/secret-4.yaml
70+
file: ~/exercises/resources-v4/secret-3b.yaml
7171
```
7272

7373
Processing this with ``ytt``:
7474

7575
```terminal:execute
76-
command: ytt -f resources-v4/random.star -f resources-v4/secret-4.yaml -f resources-v4/values.yaml
76+
command: ytt -f resources-v4/random.star -f resources-v4/secret-3b.yaml -f resources-v4/values.yaml
7777
```
7878

7979
we get:
@@ -92,7 +92,7 @@ stringData:
9292
which is the same as we had for the prior version, but overriding the password:
9393

9494
```terminal:execute
95-
command: ytt -f resources-v4/random.star -f resources-v4/secret-4.yaml -f resources-v4/values.yaml -v password1=top-secret
95+
command: ytt -f resources-v4/random.star -f resources-v4/secret-3b.yaml -f resources-v4/values.yaml -v password1=top-secret
9696
```
9797

9898
now yields:

0 commit comments

Comments
 (0)