Skip to content

v0.4.0

Compare
Choose a tag to compare
@github-actions github-actions released this 27 Jun 18:18
· 1172 commits to main since this release
309b146

FEATURE: New tcpTunnel backend mode allowing for private sharing of local TCP sockets with other zrok users (#170)

FEATURE: New udpTunnel backend mode allowing for private sharing of local UDP sockets with other zrok users (#306)

FEATURE: New metrics infrastructure based on OpenZiti usage events (#128). See the v0.4 Metrics Guide for more information.

FEATURE: New limits implementation based on the new metrics infrastructure (#235). See the v0.4 Limits Guide for more information.

FEATURE: The invite mechanism has been reworked to improve user experience. The configuration has been updated to include a new invite stanza, and now includes a boolean flag indicating whether or not the instance allows new invitations to be created, and also includes contact details for requesting a new invite. These values are used by the zrok invite command to provide a smoother end-user invite experience #229)

FEATURE: New password strength checking rules and configuration. See the example configuration file (etc/ctrl.yml) for details about how to configure the strength checking rules (#167)

FEATURE: A new admin/profile_endpoint configuration option is available to start a net/http/pprof listener. See etc/ctrl.yml for details.

CHANGE: The controller configuration version bumps from v: 2 to v: 3 to support all of the new v0.4 functionality. See the example ctrl.yml for details on the new configuration.

CHANGE: The underlying database store now utilizes a deleted flag on all tables to implement "soft deletes". This was necessary for the new metrics infrastructure, where we need to account for metrics data that arrived after the lifetime of a share or environment; and also we're going to need this for limits, where we need to see historical information about activity in the past (#262)

CHANGE: Updated to latest github.com/openziti/sdk-golang (#335)

FIX: zrok share reserved --override-endpoint now works correctly; --override-endpoint was being incorrectly ignore previously (#348)