From 3c95fe63805d32914b05214334b8d57f65e89cc5 Mon Sep 17 00:00:00 2001 From: Kingdon Barrett Date: Tue, 13 Apr 2021 15:08:38 -0400 Subject: [PATCH] change one word Signed-off-by: Kingdon Barrett --- docs/use-cases/gh-actions-manifest-generation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/use-cases/gh-actions-manifest-generation.md b/docs/use-cases/gh-actions-manifest-generation.md index 6550c506..64641e39 100644 --- a/docs/use-cases/gh-actions-manifest-generation.md +++ b/docs/use-cases/gh-actions-manifest-generation.md @@ -1112,7 +1112,7 @@ The [Sops Binary Installer] action enables more advanced use cases, like encrypt While much of this type of manipulation could be handled in `Kustomization`'s `postBuild`, via `envsubst`, some configurations are more complicated this way. They can be better handled in CI, where access to additional tools can be provided. -By writing YAML manifests into a Git commit, the same manifests as `Kustomize` directly applies, they can be saved for posterity. Or projected out into a new pull request where they can be reviewed before application, or with the proper safe-guards in place they can be applied immediately through a more direct-driven automation. +By writing YAML manifests into a Git commit, the same manifests that `Kustomize` directly applies, they can be saved for posterity. Or projected out into a new pull request where they can be reviewed before application, or with the proper safe-guards in place they can be applied immediately through a more direct-driven automation. With generated YAML that Flux applies in the cluster directly from Git commits, **fui-yoh** - that's GitOps!