Closed Zebradil closed 3 months ago
For my intents and purposes ignoring the entire .myks by default would be fine. It could contain a commented out line to stop ignoring vendir-cache
Added more info here: https://github.com/mykso/myks/blob/main/docs/optimizations.md#speed-up-cicd-pipelines
This PR updates the
.gitignore
file that is created by themyks init
command to reflect the latest changes in the.myks
directory.UPD: decided to just exclude the whole
.myks
directory by default.With these changes, the following files are ignored:
.myks/tmp
: data schema and values files managed bymyks
and refreshed on every run.myks/envs/**/helm
: helm values files generated bymyks
on every render of this app.myks/envs/**/steps
: yaml files with intermediate results of the rendering steps.myks/envs/**/argocd_defaults.ytt.yaml
: generated on every run default data values for the ArgoCD pluginWhat is not ignored by default (these files are useful for debugging and tracking upstream changes in PRs):
.myks/vendir-cache
: vendir cache entries.myks/envs/**/env-data.yaml
: generated data values files for environments, useful to see the final definition of an environment.myks/envs/**/vendor
: directory with links to the vendir cache entries.myks/envs/**/vendir-links.yaml
: map of vendor directories to cache entries.myks/envs/**/vendir.yaml
: generated vendir configuration file for this applicationIt feels like we can completely ignore the
.myks
directory by default and provide hints to users to include some of the ignored files and directories to satisfy particular use cases.