Releases: VITObelgium/fakes3pp
Releases · VITObelgium/fakes3pp
v4.1.0
chart-v1.3.0
What's Changed
A new chart release to use the latest version of the proxy with extra contextual info in the request log
Full Changelog: v4.1.0...chart-v1.3.0
chart-v1.2.0
What's Changed
When additional ingress routes are available it is important that the s3proxy is aware of them. This can now be specified in helm.
Full Changelog: chart-v1.1.4...chart-v1.2.0
chart-v1.1.4
v4.0.0
What's Changed
- feature: log upstream HTTP status by @pvbouwel in #56
- Support 2 listeners against main by @pvbouwel in #58
- helm: add chart by @pvbouwel in #59
Breaking changes were introduced to make config clearer:
breaking change: shared config names
FAKES3PP_S3_PROXY_JWT_PRIVATE_RSA_KEY => FAKES3PP_PROXY_JWT_PRIVATE_RSA_KEY
FAKES3PP_S3_PROXY_JWT_PUBLIC_RSA_KEY => FAKES3PP_PROXY_JWT_PUBLIC_RSA_KEY
The following environment variables have changed name and semantics:
FAKES3PP_S3_PROXY_KEY_FILE => FAKES3PP_S3_PROXY_TLS_KEY_FILE
FAKES3PP_S3_PROXY_CERT_FILE => FAKES3PP_S3_PROXY_TLS_CERT_FILE
FAKES3PP_S3_PROXY_PORT => FAKES3PP_S3_PROXY_TLS_PORT
FAKES3PP_STS_PROXY_PORT => "FAKES3PP_STS_PROXY_TLS_PORT"
FAKES3PP_STS_PROXY_CERT_FILE => "FAKES3PP_STS_PROXY_TLS_CERT_FILE"
FAKES3PP_STS_PROXY_KEY_FILE => "FAKES3PP_STS_PROXY_TLS_KEY_FILE"
As the new name implies they can only be used to setup a TLS listener.
If a user wants to have a plain text listener they should use
the new environment varibles:
FAKES3PP_S3_PROXY_HTTP_PORTFAKES3PP_STS_PROXY_HTTP_PORT
Full Changelog: v3.11.1...v4.0.0
chart-v1.1.1
What's Changed
Full Changelog: chart-v1.1.0...chart-v1.1.1
chart-v1.1.0
What's Changed
Full Changelog: v4.0.0...chart-v1.1.0