Releases: shieldproject/shield-boshrelease
Releases · shieldproject/shield-boshrelease
Release list
S.H.I.E.L.D. BOSH Release v6.4.1
Improvements
- Allow overrides for store / target / job autoprovisioning.
Fixes #46
S.H.I.E.L.D. BOSH Release v6.4.0
Improvements
- Upgraded to SHIELD 0.7.2, which includes many fixes.
You may want to check those Release Notes (0.7.1
and 0.7.2 were minor bumps for pipeline reasons) - New
shield.agent.ipproperty, for when you just can't rely on
IP address auto-detection (i.e. when deploying viabosh-init),
and you still want to auto-provision stuff. - You can now use the autoprovisioning features of the
shield-agentjob to provision out your Schedules and Retention
Policies. Automatically. Life is good. - You can now disable SSL/TLS on the SHIELD Web UI / API.
This isn't recommended, but you can do it. - Job spec file property definitions are more accurately
described. If you like to read raw spec files to figure out how
to use BOSH releases, you're welcome.
Deprecated Things
- Singular auto-provisioning properties (
shield.job,
shield.target,shield.store,shield.scheduleand
shield.retentionare no longer supported. Use the map-based
plural variants instead. - Auto-provisioning on the
shield-daemonjob is now deprecated.
All object types can be provisioned by theshield-agentjob.
Unless you are running a SHIELD without an agent, you won't
notice a thing.
S.H.I.E.L.D. BOSH Release v6.3.6
Improvements
- You can now create multiple stores/retention policies/schedules/targets
via the BOSH manifest. Previously only one of each was allowed in a manifest.
Bug Fixes
- Fixed issue with the shield-agent post-start script
failing the first time it was creating a target.
shield
Bumped https://github.com/starkandwayne/shield to v0.6.6
Thanks
Many thanks to @karampok, @gogolok, @frodenas, and @fearoffish for their work on this
release!
S.H.I.E.L.D. BOSH Release v6.3.5
Bug Fixes
- Fixed bug in autoprovisioning of stores, retention policies, and schedules.
- Added the utils package to the agent
S.H.I.E.L.D. BOSH Release v6.3.4
Bug Fixes
- Fixed issue where shield-agent was not provided the daemon port + hostname,
required for auto-configuration of shield-agent
S.H.I.E.L.D. BOSH Release v6.3.3
shield
Bumped https://github.com/starkandwayne/shield to v0.6.5
S.H.I.E.L.D. BOSH Release v6.3.2
Core Enhancements
- SHIELD now works with MySQL and MariaDB databases. Use the configuration
optiondatabase_typeto set the database driver tomysql.
Bug Fixes
- Add a timeout of 20 seconds to the curl call that retrieves the
public key from the SHIELD core, to avoid deadlock conditions
that arise when the start script cannot access the core, either
due to networking issues, naming problems, or firewall / ACLs. - Fixes a bug where
shield list jobs --paused/--unpausedis reversed.
S.H.I.E.L.D. BOSH Release v6.3.1
Improvements
- Users can now specify custom paths for running SHIELD plugins in their agents
with theshield.agent.plugin_pathsarray.
S.H.I.E.L.D. BOSH Release v6.3.0
Improvements
- Revamped SSH key support for agent/daemon communication.
The SSH key is now required to be input, rather than having
a key tied to stemcells + upgrades. Made property names more
relevant for ssh key related properties.
Job Property Renames/Removals
- The
shield.daemon.host_keyproperty is no longer used. It has
been replaced byshield.daemon.ssh_private_key, with no default
value. This must be specified in your manifest - The
shield.agent.authorized_keysproperty is no longer used. It
has been replaced byshield.agent.daemon_public_key. The new value
is a scalar of the public key corresponding toshield.daemon.ssh_private_key,
whereas the old property was an array. The agent will continue to use this
in conjunction with any key found via theshield.agent.autoprovision
detection. - The
shield.agent.authorize_generated_daemon_keyhas been removed. It is no longer
necessary, since the daemon key is no longer generated behind the scenes.
shield
Bumped https://github.com/starkandwayne/shield to v0.6.4
S.H.I.E.L.D. BOSH Release v6.2.2
Release Notes
- Fixes a bug with the Postgres restore plugin where the restore would fail if any given line in the dump file was too long.
- Fixes a bug where an initial run of
create backendwould fail if the user's home directory was on a different filesystem than/tmp. - The backend name is now displayed in the CLI when executing a command, in addition to its IP.
- The help dialogues for the
backendcommands now give the flags required. - The shield plugins will no longer display the endpoint argument (potentially along with credentials contained within) in the process name.