You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This program walks a hierarchy of Argo CD Application templates, renders Kubernetes manifests from the input templates, and posts the rendered files back for the user to review and validate.
5
+
This program walks a hierarchy of Argo CD Application templates, renders Kubernetes manifests from the input templates, and posts the rendered files back for the user to review and validate.
6
6
7
-
It is designed to be called from a CI job within a pull request, enabling the author to update templates and see the resulting manifests directly within the pull request before the changes are applied to the Kubernetes cluster.
7
+
It is designed to be called from a CI job within a pull request, enabling the author to update templates and see the resulting manifests directly within the pull request before the changes are applied to the Kubernetes cluster.
8
8
9
9
The rendered manifests are kept within the repository, making diffs between revisions easy to parse, dramatically improving safety when updating complex application templates.
10
10
@@ -19,8 +19,8 @@ The rendered manifests are kept within the repository, making diffs between revi
19
19
20
20
🫵 Submit a PR where you make a change to the overrides of the [`demo`](demo/README.md), and you'll see the [Github action]([README](../../.github/workflows/generate-manifests-demos.yaml)) add a commit to your PR with the resulting changes.
@@ -44,7 +44,7 @@ The command will be called with the output directory as the first argument (e.g.
44
44
45
45
---
46
46
47
-
## Pre-requisites
47
+
## Pre-requisites
48
48
49
49
This is for a new user that is looking to use mani-diffy on a new repo.
50
50
@@ -55,7 +55,7 @@ In order to make use of mani-diffy on the repo that holds all of your ArgoCD app
55
55
56
56
`mani-diffy` itself makes no assumptions about how the repo is structured, as long as it can successfully render the charts it encounters while walking the Application tree.
57
57
58
-
However, you may find it useful to organize your repo similarly to the demo app, with 3 key directories :
58
+
However, you may find it useful to organize your repo similarly to the demo app, with 3 key directories :
59
59
60
60
1. a "root" or "bootstrap" directory that holds all the ArgoCD applications manifests.
61
61
2. a "charts" directory that contains all the helm charts needed for the ArgoCD applications.
0 commit comments