Skip to content

shield Release v0.7.0
Compare
Choose a tag to compare
@starkandwayne-bot starkandwayne-bot released this 31 Oct 20:27
· 1363 commits to master since this release
v0.7.0
afd2687

NOTE: Prior to 0.7.0 of SHIELD, the fs plugin had a nasty bug that would manifest if you had more than one fs-based backup (target or store) configured on the same agent. Users are advised to upgrade to 0.7.0 if they wish to make use of filesystem-based backups!

Improvements

  • The CLI now displays the store / target / schedule / retention
    policy names, alongside UUIDs in the Job creation TUI forms.
    Fixes #195.

  • shield show tasks now honors the --limit parameter, so you
    don't have to look at all the tasks. Fixes #164.

  • shield backend now prints the currently selected backend.
    Fixes #194

  • Both the Web UI and the CLI now lowercase plugin names before
    submitting them to the Rest API. Fixes #156

  • The postgres plugin once again allows users to customize the path
    to postgres binaries via the pg_bindir target configuration parameter.

    NOTE This re-introduces a feature that was previously removed, using
    the same configuration. Take care to insure that any targets you have
    configured are no longer specifying this key, as it was ignored until now.
    If it is specified, ensure that it is the correct value, or remove it, if
    it is unneeded. If it is specified and is an invalid value, your postgres
    backups will start to fail after upgrading.

  • Releases should now include both the SHIELD CLI (built for
    various platforms) and also the server components, available as a
    tarball for different platforms / architectures. This tarball
    contains: shield-schema, shield-agent and shieldd, all
    supported plugins, and the static assets for the SHIELD Web UI
    (in webui/). Fixes #217

  • Backup and Restore operations now bail out if no data is
    detected on the input side of the stream. That is, if a backup
    plugin misbehaves and doesn't send any data to be backed up, the
    job will fail. Likewise, if a restore doesn't pull any data
    back from the remote store, the operation fails. This is
    considered a good thing.

Bug Fixes

  • Dropdowns on the Job Edit Form now remember the values the Job
    had before you opened the form. Fixes #173
  • The mysql plugin can now be used to backup and restore all
    databases. Fixes #211
  • The fs plugin just plain didn't work; it would happily write
    to the (regular) file /dev/st0, but not to standard output.
    Similarly, on restore, it would read from /dev/st0, not standard
    input. This caused our testing (one fs-based backup) to pass,
    but didn't work out so well in the real world. Mitigations have
    been put in place to ensure that plugins send backup data to the
    store plugin.
  • The fs plugin now creates the base directory if it does not
    already exist, allowing for complete restore from a backup.
Assets 5
Loading