depot - monorepo for the virus lounge

Age	Commit message (Collapse)	Author	Files	Lines
2019-09-04	fix(context): Ensure resource set paths are made absolute	Vincent Ambo	1	-9/+9
	Resolving of files (for `insertFile` and `insertTemplate`) should always be relative to the resource set location, the previous behaviour was considered a bug. This is fixed by ensuring that resource set paths are absolute at context loading time.
2018-12-11	feat(main): Support specifying kubectl args in ResourceSets	Martin Lehmann	1	-0/+36

2018-06-26	test(context): Introduce an explicit value merging test	Vincent Ambo	1	-0/+22
	Introduces a test which will merge variables defined at every possible layer together and ensure that the loaded context configuration is as expected. The test data provides an actual resource set template that can be tested locally from a kontemplate source checkout: kontemplate template context/testdata/merging/context.yaml --var cliVar=cliVar
2018-06-26	chore(context): Remove previous value override test	Vincent Ambo	1	-23/+0

2018-06-09	feat(context): Support loading import variables from absolute paths	Vincent Ambo	1	-8/+8
	This lets users specify the paths from which to import additional variables using absolute paths in addition to relative paths. This enables both loading of configuration files placed outside of the resource set folder (if desired), as well as special use-cases such as specifying `/dev/stdin` as an input path to read variables from standard input. This change supersedes #131
2018-06-09	refactor(context): Implement more explicit merging of variables	Vincent Ambo	1	-23/+37
	The hierarchy for loading variables was previously not expressed explicitly. This commit refactors the logic for merging variables to explicitly set the different layers of variables as values on the context object and merge them for each resource set in `mergeContextValues`.
2018-06-09	feat(context): allow explicit variables to be defined as argument	Phillip Johnsen	1	-0/+22
	These changes allows variables to be defined when executing `kontemplate` via one or more `--variable` arguments. With this in place one can either define new variables or override existing variables loaded from a file: ``` $ kontemplate apply --variable version=v1.0 example/fancy-app.yaml ``` This avoids the need to write variables into a temporary file that is only needed to provide "external variables" into resource sets. Closes https://github.com/tazjin/kontemplate/issues/122
2017-11-21	feat(license): Relicense under GPLv3	Vincent Ambo	1	-0/+9
	All further kontemplate source code changes and releases will happen under the GPLv3. Previous releases are still available under the MIT license.
2017-07-13	feat context: Allow overriding resource set paths	Vincent Ambo	1	-0/+68
	Instead of always inferring the path at which files in a resource set are located, let users override the path by specifying a `path` field. This makes it possible to add the same resource set multiple times with different values while still keeping distinct names for addressability (for example when using include/exclude). This fixes #70
2017-07-03	feat context: Add ability to import extra variables from files	Vincent Ambo	1	-0/+44
	Kontemplate context specifications can now load extra variables from YAML or JSON files by specifying a list of files (relative to the context file) under the `import` key.
2017-04-04	fix test: Assert variable override order	Vincent Ambo	1	-0/+5

2017-04-04	feat context: Support resource set default values	Vincent Ambo	1	-0/+14
	This adds functionality to specify default values directly in resource sets. The idea is that users can create a file called `values.yaml` or `values.json` in a resource set's folder and have all variables specified in that file be automatically merged into the resource set variables with the lowest priority. This fixes #25 This fixes #30 (to a degree)
2017-02-20	style: Apply go fmt	Vincent Ambo	1	-2/+2

2017-02-14	feat ctx: Let sub-resource-sets inherit vars from parent	Vincent Ambo	1	-0/+59
	Users of kontemplate may expect variables defined on the parent resource to be inherited by children. This implements that functionality. Values defined twice are overwritten by the child's definition. Fixes #20
2017-02-08	feat context: Add deserialisation tests	Vincent Ambo	1	-0/+83