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
The data saved for each peer'd server in the registry does not include its properties. I have not been able to figure out how to push that data from the connected zetta client to the zetta "cloud" instance after a peer connection is established.
I imagined an event like "_peer/properties" sent over the connection once it's established, and again after any call to Zetta.prototype.properties. But nothing I've tried has worked.
Can you guys point me towards a possible solution?
The text was updated successfully, but these errors were encountered:
Feature Request
When hitting the root "cloud" instance, each server object in the returned
links
collection includes that server instance's customproperties
.So Far
I've updated
_renderRoot
in lib/api_resources/root.js to includeproperties
, which covers the root server "rel" entry.What's Next
The data saved for each peer'd server in the registry does not include its
properties
. I have not been able to figure out how to push that data from the connected zetta client to the zetta "cloud" instance after a peer connection is established.I imagined an event like "_peer/properties" sent over the connection once it's established, and again after any call to
Zetta.prototype.properties
. But nothing I've tried has worked.Can you guys point me towards a possible solution?
The text was updated successfully, but these errors were encountered: