Releases: nspcc-dev/neofs-rest-gw
v0.11.1
v0.11.0
v0.10.1
v0.10.0
Fixed
- Documentation for the
server
section (#220) - "unknown config parameter listen-address" warning (#220)
Changed
external-address
configuration behavior to include scheme (#218)- Timestamp is no longer logged if program is not running in TTY (#222)
Updating from 0.9.0
Notice that the configuration parameter external-address
in the server.endpoints
section now also includes the scheme (http/https), not just the host and port. If external-address
is not set, it will be generated from address
and tls.enabled
.
v0.9.0
Added
- HEAD request handling for documentation (#199)
- Darwin binaries (#204)
network-info
path to request network parameters (#198)- Proper TLS server support (#200)
- DefaultTimestamp configuration (#209)
- New upload/download APIs (#206, #210, #211, #214)
Changed
- github.com/nspcc-dev/neofs-sdk-go dependency to v1.0.0-rc.12 (#191, #176, #212)
- golang.org/x/net dependency to 0.23.0 (#201)
- Documentation to reflect known limitations (#196)
- github.com/nspcc-dev/neofs-api-go/v2 is no longer used (#176)
- Server listener configuration to conform to other NeoFS services (#200)
- github.com/nspcc-dev/neo-go dependency to v0.106.0 (#208)
Updating from 0.8.3
Notice that configuration parameters in the server
section were reorganized. For example e.g.server.schema
and tls-listen-limit
were removed, and some others were moved inside the array endpoints
. Check your configuration with the help of the gate-configuration.md and config. Also, flags in the command arguments were changed.
A new upload object request has been introduced: /objects/{containerId}
. This is a POST request that accepts the X-Attributes
header, where all custom object attributes can be included in a JSON-formatted key-value map. Also, new GET and HEAD requests are added for object downloading: /objects/{containerId}/by_id/{objectId}
and /objects/{containerId}/by_attribute/{attrKey}/{attrVal}
. For more information, see the migration documentation. In the future, we plan to use these requests as the only option for object upload and download. We recommend starting to use them now.