Due to protocol versioning, it is highly recommended to keep relays up to date. This release simplifies the process, bringing automatic relay upgrade functionality, including an upgrade supervisor, migration support and update channels.
When auto_upgrade
is set to true
or not present in the relay
config.json
, the relay will attempt automatic upgrades whenever it
receives an update notification from the directory during heartbeat on
the update channel specified in the enrollment config. If an upgrade
fails, a best-effort rollback is performed and the affected version is
skipped.
The relay update channels supported by the directory and the respective
latest version is exposed via the directory’s /info
endpoint.
{
"auto_upgrade": true,
"contracts": {
"https://contract1.example.com": {
"update_channel": "default"
}
}
}
This sequence diagram shows the high-level flow of a relay
upgrade and
the behind the scenes interaction it has with other Wireleap components.
relay
directory
client
Added 2s start delay for process health verification.
UI fixes and improvements:
null
whitelist are no longer treated equally.contract
auth
ps-dummy
ps-stripe
Version
0.2.1
Previous Article
Multiplexing, UDP and TUN device supportNo results found
client
=dataflow
'circuit
!docs
^installation
paper$
White space acts as an AND operator, while a single pipe
(|
) character acts as an OR operator. To escape
white space, use double quotes such as ="wireleap
client"
for an exact match.