Reduce neofs-lens storage inspect
flags restrictions
#2549
Labels
enhancement
Improving existing functionality
I3
Minimal impact
neofs-lens
NeoFS Lens app issues
S4
Routine
U3
Regular
Milestone
Is your feature request related to a problem? Please describe.
#2543 is going to be merged (if you are reading this, it is probably done), and
neofs-lens storage inspect
(orget
) requires SN's config to read storage correctly. So strict requirement. There can be situations when a user does not have access to a config (or config is lost).Describe the solution you'd like
Analyze and find out if it is possible to just specify paths to shards and derive their config on the fly without the need to look for a config (or write from scratch, which is even worse). There must not be any duality of a shard configuration understanding and if an object is placed correctly on some shard,
neofs-lens storage
must be able to get it.Describe alternatives you've considered
Do nothing. Missing config is a disaster for a user then.
Additional context
Blobovnicza removal should help a lot. May be related to #2497. May be fixed implicitly if the engine becomes AI and does not require config specification for already-inited shards.
The text was updated successfully, but these errors were encountered: