Skip to content
This repository has been archived by the owner on Dec 21, 2019. It is now read-only.

Version 1.6.0
Compare
Choose a tag to compare
@tazjin tazjin released this 09 Jun 19:57
· 32 commits to master since this release
v1.6.0
This tag was signed with the committer’s verified signature. The key has expired.
tazjin
GPG key ID: 66F505681DB8F43B
Expired
Verified
Learn about vigilant mode.
97bef90

This release of Kontemplate comes with the following improvements:

  • Variables can now be specified explicitly on the command line using one or more --var foo=bar flags. Variables specified in this way have the highest precedence and will override values set in other places.

    Thanks to @phillipj for contributing this feature; and to @n0madic for originally suggesting it!

  • File paths for additional variable imports can now point at absolute files.

    This change lets users specify absolute file paths in the import directive of a cluster configuration.

    In addition to referencing files in other locations on a disk this also gives users the ability to specify "special" paths such as, for example, /dev/stdin to load additional variables (in JSON or YAML format) from kontemplate's standard input.

    Thanks to @cellofellow for nudging me in the right direction to get this implemented!

  • Resource sets can now have their path set to point at a single template file.

    Instead of having to create a hierarchy of directories just to template a single file, users can now include a single template file by setting the path value appropriately:

    Example:

    context: some-context
include:
  - name: some-resource
    path: some-resource.yaml

    This will template the file some-resource.yaml from the same folder as the context configuration itself.

  • Some code has been refactored to make the hierarchy of variable merges more explicit.

Release binaries are signed with GPG key 66F505681DB8F43B which is verified on my Github profile. They are built repeatably and reproducibly using Nix.

In other notes I would like to mention that I am not currently using Kubernetes in any of my own projects as I find that the complexity of the project has tipped in a direction that I am not comfortable with.

This does not mean that kontemplate is unmaintained in any way as the tool is generally applicable for use-cases other than Kubernetes resource templating, too.

Future versions of the project may brand it slightly more in the direction of a general-purpose templater, however Kubernetes-specific functionality will not be removed.

Please keep the issues & pull requests coming & thanks for using Kontemplate!

Assets 10
Loading