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
Is your feature request related to a problem? Please describe.
I'm always frustrated when I can't tell what node versions are being used on the network. We even have nspcc-dev/neofs-contract#299.
Describe the solution you'd like
We can have version in an attribute for now. Node can set it automatically, but allow to override via config (much like #602). These attributes should be documented appropriately.
The text was updated successfully, but these errors were encountered:
It's an attribute and in general it can't be checked server-side. Maybe there is some use case for overrides as well. But I mostly mean that if you set it in the config (just like any other attribute), it should win over the default value because that's the thing written in the config and expected to be used by admin.
How (where) should the docs be placed? API? This repo?
Everywhere. Node behavior should be documented for admin, API should be documented for API users.
Is it gonna be another well-known attr?
Yep, looks like this. It doesn't affect anything at the moment, yet at the same time it's very useful to have some admin-level visibility into the system.
It is done automatically but can be overwritten if `Version` attribute is
provided via the application configuration.
Closesnspcc-dev#2455.
Signed-off-by: Pavel Karpy <[email protected]>
carpawell
added a commit
to carpawell/neofs-node
that referenced
this issue
Aug 9, 2023
It is done automatically but can be overwritten if `Version` attribute is
provided via the application configuration.
Closesnspcc-dev#2455.
Signed-off-by: Pavel Karpy <[email protected]>
Is your feature request related to a problem? Please describe.
I'm always frustrated when I can't tell what node versions are being used on the network. We even have nspcc-dev/neofs-contract#299.
Describe the solution you'd like
We can have version in an attribute for now. Node can set it automatically, but allow to override via config (much like #602). These attributes should be documented appropriately.
The text was updated successfully, but these errors were encountered: