Releases: bolcom/unFTP
Releases · bolcom/unFTP
v0.12.7
Changes in this release:
- Upgraded to libunftp 0.17.0 along with other dependencies.
v0.12.6
Changes in this release:
- Upgraded to libunftp v0.16.2 in order to fix an issue with file uploads in FTPS mode when using lftp. See bolcom/libunftp#285
v0.12.5
v0.12.4
Changes in this release:
- #73 GCS Back-end: Added support for k8s workload identity along with the
--sbe-gcs-service-account
argument. - #74 GCS Back-end: Added the
--sbe-gcs-root
argument allowing a specific path/prefix to be specified where unFTP files will reside in the bucket. - Upgraded to tokio 1.0, hyper 1.14, libunftp 0.16 and others
- Now logging the GCS auth method and the GCS root dir
- From libunftp: Handle path names that contain \r and/or \n according to rfc-2640
Discuss this release on https://t.me/unftp
v0.12.3
In this release:
- Upgraded to libunftp v0.14.1
- Upgraded other dependencies
- Upstream fix: Allow Non-ASCII / UTF-8 in path names
v0.12.2
Changes in this release
- Upgraded dependencies
- Added environment variable named
UNFTP_FTPS_REQUIRED_ON_DATA_CHANNEL
used to set whether FTPS is required on the data channel or not. - Fixed issue where building with the
pam
feature did not actually work - Readme improvements
v0.12.1
Changes in this release:
- Upgraded to libunftp v0.13.0
- Added
--ftps-required-on-data-channel
argument - Added
--ftps-required-on-control-channel
argument - Fixed an issue where REST was broken for all storage back-ends
- Added
--log-level
argument. - Fix: Don't panic if the redis logger cannot be initialized
- Turned on more aggressive compile and link time optimisation.
v0.12.0
- Upgraded to libunftp 0.12.0 which fixes a number of issues, most notably cloud storage back-end stability issues and speed improvements on the filesystem back-end.
- Fixed an issue where there were missing logging in release builds
- The
/health
and/ready
paths added to the HTTP server in the previous release now have a more useful implementation in that it will send a NOOP command to the FTP interface. - Added the
--sbe-gcs-base-url
command line argument that allows overriding the default value ofhttps://www.googleapis.com
for say testing purposes.
v0.11.0
Changes in this release:
- Log to the terminal also when using the Redis logger (#47)
- Improved logging by utilising libunftp's new structured logging
- Added the
--passive-host
command line argument (#53) to allow specifying how the IP address is determined which is sent in response to a PASV command. - Handle
SIG_INT
and log its occurrence. - Added a service home page on the HTTP root path (#56)
- Added
/health
and/ready
paths to the HTTP server. This can be utilised in Kubernetes for instance for readiness and liveness probes. At the moment these simply return HTTP 200 but this will change in future to be more useful.
v0.10.1
Changes is this release:
- Upgraded to libunftp v0.11.1