Reduce `neofs-lens storage inspect` flags restrictions #1114

New issue

Open

opened 2025-12-28 17:21:51 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:21:51 +00:00

Owner

Originally created by @carpawell on GitHub (Sep 6, 2023).

https://github.com/nspcc-dev/neofs-node/pull/2543 is going to be merged (if you are reading this, it is probably done), and neofs-lens storage inspect (or get) 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 https://github.com/nspcc-dev/neofs-node/issues/2497. May be fixed implicitly if the engine becomes AI and does not require config specification for already-inited shards.

Originally created by @carpawell on GitHub (Sep 6, 2023). ## Is your feature request related to a problem? Please describe. https://github.com/nspcc-dev/neofs-node/pull/2543 is going to be merged (if you are reading this, it is probably done), and `neofs-lens storage inspect` (or [`get`](https://github.com/nspcc-dev/neofs-node/issues/2548)) 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 https://github.com/nspcc-dev/neofs-node/issues/2497. May be fixed implicitly if the engine becomes AI and does not require config specification for already-inited shards.