Make munger begin/end less generic

Just force the beginMungeTag() endMungeTag() macros on users, by hiding
it under the covers. It really simplies things for users.
This commit is contained in:
Eric Paris
2015-07-20 12:45:12 -05:00
parent 22fd8ac32d
commit 4cbca2e63c
19 changed files with 105 additions and 78 deletions

View File

@@ -166,7 +166,7 @@ spec:
```
[Download example](pod-redis.yaml)
<!-- END MUNGE: EXAMPLE -->
<!-- END MUNGE: EXAMPLE pod-redis.yaml -->
Notes:
- The volume mount name is a reference to a specific empty dir volume.

View File

@@ -87,7 +87,7 @@ spec:
```
[Download example](pod-nginx-with-label.yaml)
<!-- END MUNGE: EXAMPLE -->
<!-- END MUNGE: EXAMPLE pod-nginx-with-label.yaml -->
Create the labeled pod ([pod-nginx-with-label.yaml](pod-nginx-with-label.yaml)):
@@ -143,7 +143,7 @@ spec:
```
[Download example](replication-controller.yaml)
<!-- END MUNGE: EXAMPLE -->
<!-- END MUNGE: EXAMPLE replication-controller.yaml -->
#### Replication Controller Management
@@ -196,7 +196,7 @@ spec:
```
[Download example](service.yaml)
<!-- END MUNGE: EXAMPLE -->
<!-- END MUNGE: EXAMPLE service.yaml -->
#### Service Management
@@ -312,7 +312,7 @@ spec:
```
[Download example](pod-with-http-healthcheck.yaml)
<!-- END MUNGE: EXAMPLE -->
<!-- END MUNGE: EXAMPLE pod-with-http-healthcheck.yaml -->
For more information about health checking, see [Container Probes](../pod-states.md#container-probes).