Deleting unnecessary maps in the config #2993
Labels
config
Configuration format update or breaking change
enhancement
Improving existing functionality
I2
Regular impact
neofs-storage
Storage node application issues
S3
Minimally significant
U3
Regular
Milestone
Is your feature request related to a problem? Please describe.
I'm always frustrated when there are fields in the config that are difficult to validate, particularly in the form of a map.
In the node config, there are fields:
node.attribute_*
storage.shard.*
Describe the solution you'd like
Make these fields lists.
Describe alternatives you've considered
Leave everything as it is, but then complex validation will remain and it will not be easy to reuse the config.
Additional context
Refs #2981 (comment).
After this, we can use viper.UnmarshalExact for validation and reuse the config in the code.
The text was updated successfully, but these errors were encountered: