Skip to content

Releases: DtxdF/overlord

v0.22.0

22 Dec 05:45

Choose a tag to compare

Changes between 0.21.0 and 0.22.0

  • Avoid displaying message integration when they don't say anything:
    • Avoid displaying the content on the client side when the server doesn't say anything meaningful.
    • Avoid including information about each integration on the server side when they doesn't say anything meaningful.
  • List integrations in a dictionary to avoid repetition.

Full Changelog: v0.21.0...v0.22.0

v0.21.0

27 Oct 05:47

Choose a tag to compare

Changes between 0.20.1 and 0.21.0

  • Added: diskLayout.disk.partitions.<partition>.format.script parameter:
    • The main motivation is to add support for ZFS, but this change also allows for more complex installations.
  • Fixed: output order in vm module.
  • Fixed: typo entrypoint -> appjailImage in diskLayout.from.type check.
  • Added: missing closing quotation mark in Makefile.
  • Fixed: usage format in libexec/install-from-components.sh script.
  • Added: support for PkgBase:
    • Added: pkgbase type for diskLayout.from.type.
    • Added: diskLayout.from.packages parameter.
    • Added: diskLayout.from.pkgConf parameter.
    • Added: diskLayout.from.fingerprints parameter.
    • Added: libexec/vm-install-from-pkgbase.sh script.
  • Fixed: reference format to appjail-ajspec(5) in overlord-spec(5).
  • Refer to parameters using their absolute name in diskLayout.* checks.
  • Added: missing check for diskLayout.from.components items.
  • Added: install-files and uninstall-files targets.

Full Changelog: v0.20.1...v0.21.0

v0.20.1

23 Oct 16:41

Choose a tag to compare

Changes between 0.20.0 and 0.20.1

  • Fixed: NameError: name 'overlord' is not defined in metadata spec.

Full Changelog: v0.20.0...v0.20.1

v0.20.0

22 Oct 05:01

Choose a tag to compare

Changes between 0.19.1 and 0.20.0

  • Added: metadataParameter to metadata deployments.

Full Changelog: v0.19.1...v0.20.0

v0.19.1

24 Sep 21:37

Choose a tag to compare

Changes between 0.19.0 and 0.19.1

  • Don't specify datastore when it's not specified in the deployment file:
    • When creating the profile for the virtual machine, the data store is specified even if the user does not include it in the deployment file, so on the API server the value is converted to a string, causing /None to be used as the data store.

Full Changelog: v0.19.0...v0.19.1

v0.19.0

18 Sep 19:56

Choose a tag to compare

Changes between 0.18.0 and 0.19.0

  • Added: support for appConfig deployments in cancel
  • Display only the first matching metadata in print-template
    • Currently, when print-template finds metadata in a chain, it prints it. However, to achieve the same behavior as in apply it is better to simply exit after printing the processed appConfig.

Full Changelog: v0.18.0...v0.19.0

v0.18.0

16 Sep 20:23

Choose a tag to compare

Changes between 0.17.2 and 0.18.0

  • Added: print-template subcommand.
  • Documented: missing parameters for print-spec subcommand
  • Added: --mako-directories parameter in {apply,destroy}
    • Fix Template 'memory:0xXXXXXXXXXXXX' has no TemplateLookup associated exception when using a tag like %include.

Full Changelog: v0.17.2...v0.18.0

v0.17.2

15 Sep 01:00

Choose a tag to compare

Changes between 0.17.1 and 0.17.2

  • Fixed: TypeError: _destroy() missing 1 required positional argument: 'filter_root_chain'
    • This only affects appConfig deployments.

Full Changelog: v0.17.1...v0.17.2

v0.17.1

13 Sep 01:03

Choose a tag to compare

Changes between 0.17.0 and 0.17.1

  • Fixed: logic when filtering chains in destroy subcommand:
    • If no filter is specified, the root chain is excluded anyway, which is not desirable.

Full Changelog: v0.17.0...v0.17.1

v0.17.0

03 Sep 22:45

Choose a tag to compare

Changes between 0.16.0 and 0.17.0

  • Added: --filter-root-chain to destroy subcommand.

Full Changelog: v0.16.0...v0.17.0