Currently the peers entry in config.yaml only updates when fission setup is run... so, if the peer list changes, this won't be reflected. We can periodically re-fetch this. We already check >= once per day for new CLI releases, we could check peers then or we can update the peer list if there is a connection failure (assume that the old peers may not be valid and get the latest list).
Currently the
peersentry inconfig.yamlonly updates whenfission setupis run... so, if the peer list changes, this won't be reflected. We can periodically re-fetch this. We already check >= once per day for new CLI releases, we could check peers then or we can update the peer list if there is a connection failure (assume that the old peers may not be valid and get the latest list).