Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 28 million developers.Sign up
SHIELD 8.x is still beta software; not recommended for production deployment
azureplugin now features a
path_prefixsetting to allow
sharing of a single Azure Blobstore container amongst several
jobs and/or SHIELDs.
fsplugin no longer relies on the
function; instead, all tarball creation / extraction is handled
directly by the plugin code, making it easier to deploy.
purgetasks that are scheduled in the
slow loop are now skipped if the Vault is sealed. This keeps
the task list from growing with lots of tasks that will not be
scheduled until later. For
purgetasks this wasn't a huge
deal, but for
test-storeit meant that cloud storage would get
slammed with test after test after test after test as soon as
the SHIELD was unlocked.
fsplugin no longer functions as a store plugin. This
configuration was deemed to dangerous in the wild, given the
locality constraints. If you need local-ish filesystem-backed
storage, check out the
WebSocket broadcast receivers are only registered after a
successful upgrade from plain HTTP to WebSockets, to avoid
stalling out the core on badly-behaved clients.
The CLI now honors
-keverywhere it appears.
It is now possible to update a target / store that was created
without any configuration (no
CLI update-* commands now properly display the updated object
attributes, instead of an empty report.
create-auth-tokenCLI command now honors
short, form submissions would "remember" their previous onsubmit
handlers, leading to some very interesting errors on both
client- and server-side.