Releases: DtxdF/overlord
Releases · DtxdF/overlord
v0.22.0
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
Changes between 0.20.1 and 0.21.0
Added:diskLayout.disk.partitions.<partition>.format.scriptparameter:- The main motivation is to add support for ZFS, but this change also allows for more complex installations.
Fixed: output order invmmodule.Fixed: typoentrypoint->appjailImageindiskLayout.from.typecheck.Added: missing closing quotation mark in Makefile.Fixed: usage format inlibexec/install-from-components.shscript.Added: support for PkgBase:Added:pkgbasetype fordiskLayout.from.type.Added:diskLayout.from.packagesparameter.Added:diskLayout.from.pkgConfparameter.Added:diskLayout.from.fingerprintsparameter.Added:libexec/vm-install-from-pkgbase.shscript.
Fixed: reference format toappjail-ajspec(5)inoverlord-spec(5).- Refer to parameters using their absolute name in
diskLayout.*checks. Added: missing check fordiskLayout.from.componentsitems.Added:install-filesanduninstall-filestargets.
Full Changelog: v0.20.1...v0.21.0
v0.20.1
Changes between 0.20.0 and 0.20.1
Fixed:NameError: name 'overlord' is not definedin metadata spec.
Full Changelog: v0.20.0...v0.20.1
v0.20.0
Changes between 0.19.1 and 0.20.0
Added:metadataParametertometadatadeployments.
Full Changelog: v0.19.1...v0.20.0
v0.19.1
Changes between 0.19.0 and 0.19.1
- Don't specify
datastorewhen 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
/Noneto be used as the data store.
- 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
Full Changelog: v0.19.0...v0.19.1
v0.19.0
Changes between 0.18.0 and 0.19.0
Added: support forappConfigdeployments incancel- Display only the first matching metadata in
print-template- Currently, when
print-templatefinds metadata in a chain, it prints it. However, to achieve the same behavior as inapplyit is better to simply exit after printing the processedappConfig.
- Currently, when
Full Changelog: v0.18.0...v0.19.0
v0.18.0
Changes between 0.17.2 and 0.18.0
Added:print-templatesubcommand.Documented: missing parameters forprint-specsubcommandAdded:--mako-directoriesparameter in{apply,destroy}- Fix
Template 'memory:0xXXXXXXXXXXXX' has no TemplateLookup associatedexception when using a tag like%include.
- Fix
Full Changelog: v0.17.2...v0.18.0
v0.17.2
Changes between 0.17.1 and 0.17.2
Fixed:TypeError: _destroy() missing 1 required positional argument: 'filter_root_chain'- This only affects
appConfigdeployments.
- This only affects
Full Changelog: v0.17.1...v0.17.2
v0.17.1
Changes between 0.17.0 and 0.17.1
Fixed: logic when filtering chains indestroysubcommand:- 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
Changes between 0.16.0 and 0.17.0
Added:--filter-root-chaintodestroysubcommand.
Full Changelog: v0.16.0...v0.17.0