Repository navigation
Releases: sebastocorp/osproxy
Releases · sebastocorp/osproxy
Release list
v0.6.3
v0.6.2
FIX:
- set log response field with source request result
v0.6.1
FIX:
- Default logs structs: add default request and response structs in logs
v0.6.0
BREAKING CHANGES:
- Types in PascalCase: previously all types were written in camelCase, now they must be written in PascalCase
- New environment variables pattern: previously the pattern to detect an environment variable in the config and replace it with its value was
$VARor${VAR}, now the pattern is${ENV:VAR}$
FEATURES:
- New regex modifier type: now you have the possibility to modify the path using a regex pattern with the modifier type PathRegex
v0.5.2
Feat:
- Object metadata in PostObject reaction: previously the sent object only had the bucket and the path, now it has a metadata field where the request headers are added
v0.5.1
Fix:
- use trim prefix instead trim sufix in object creation in PostObject response reaction
v0.5.0
BREAKING CHANGES:
- upgrade to v1alpha5 api:
- list of different sources of different object storage providers: previously you only can define 1 source of s3 or gcs, now you can define a list of sources and you can use it in any of the routes source field
- list of request modifiers: previously you only can define 1 request modifier by route, now you can define a list of modifiers and use it in the route modifiers list
- response reactions: previously you only can store the action in a pool, this pool was consumed by another worker process, and only execute an http request, now you can execute an action by a condition that use the response of the backend to trigger
- rewrite of the sources clients: previously we use the minio and gcs sdks clients, now we use the http client of golang and craft the request with the signatures
osproxy-helm-chart-0.3.0
A Helm chart for osproxy, HTTP proxy to serve object storage files
v0.4.1
BREAKING CHANGES:
- upgrade to v1alpha4:
- change source field name to requestRouting
- header value routing: now you can route to your backend buckets with a header value as reference
v0.3.8
BREAKING CHANGES:
- healthz endpoint
- upgrade to v1alpha3:
- now the backend object is not set in this service
- default source relation can be set as osproxy-source-default
- action worker: now the action by error in object download is handle in parallel component
- max capacity in action pool: the action worker pool capacity can be set in config