Releases: pivotal-cf/service-backup-release
Releases · pivotal-cf/service-backup-release
v18.4.1-beta2
Continuing testing of pipeline migration to runway&redis, beta2 tag
v18.4.1-beta
Testing pipeline migration to Runway. Please disregard this release.
v18.4.0
Fixed Issues
- Timestamps are now logged in a human-readable format.
- Fixed an issue where sending alerts was being attempted, even though alerting configuration was not provided.
- Updated Go to v1.16.3.
- Updated to use go mod and updated all dependencies to their latest versions.
Known Issues
There are no known issues with this release.
v18.3.5
- Bumped Go to 1.13.6
v18.3.4
v18.3.3
v18.3.2
v18.3.1
v18.3.0
New Features
-
Updates golang to v1.12.5
-
Improved testing to verify the case when a service-backup process is stopped with a SIGTERM, it should signal cron process manager and not start a new backup.
Known Issues
There are no known issues for this release.
v18.2.0
v18.2.0
New Features
- For Azure backups, if you aren't connecting to an Azure Public region, you can configure
endpoint
for the base endpoint name. For more details on configuration options for this property, see the Azure documentation here
Fixed Issues
- Fixes issue with
scp
(secure copy) where it triggered an error copying files using.
as the source directory. This was due to scp no longer allowing the use of.
as a source directory as fix for CVE-2018-20685. See here for details of stemcells containing the affected version of scp. - Updates golang to v1.12.1.
Known Issues
There are no known issues for this release.