You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
The key has expired.
0.1.8 (2021/03/09)
Changes/Deprecations
api: A few functions have changed places. Notably, instead of ResponseMap()
and ResponseBody(), resources simply expose Response(). This higher-level
response object contains the map and body, and also exposes StatusCode() in
place of indivdidual resources. PR
cli: In json output format, a resource item is now an object under the
top-level key item; a list of resource items is now an list of objects under
the top-level key items. This preserves the top level for putting in other
useful information later on (and the HTTP status code is included now). PR
cli: In json output format, errors are now serialized as a JSON object with
an error key instead of outputting normal text PR
cli: All errors, including API errors, are now written to stderr. Previously
in the default table format, API errors would be written to stdout. PR
cli: Error return codes have been standardized across CLI commands. An error
code of 1 indicates an error generated from the actual controller API; an
error code of 2 is an error encountered due to the CLI command's logic; and
an error code of 3 indicates an error that was caused due to user input to
the command. (There is some nuance sometimes whether an error is really due to
user input or not, but we attempt to be consistent.) PR
New and Improved
list filtering: Listing now supports filtering results before being returned
to the user. The filtering takes place server side and uses boolean
expressions against the JSON representation of returned items. See the
documentation
for more details. (PR 1)
(PR 2)
(PR 3)
server: Officially support reloading TLS parameters on SIGHUP. (This likely
worked before but wasn't fully tested.)
(PR)
server: On SIGHUP, worker
tags will be
re-parsed and new values used
(PR)
server: In addition to the existing tls_min_version listener configuration
value, tls_max_version is now supported. This should generally be left blank
but can be useful for situations where e.g. a load balancer has broken TLS 1.3
support, or does not support TLS 1.3 and flags it as a disallowed value.