nspcc-dev / nspcc-dev/neofs-node
Improve default config paths for neofs-cli and neofs-adm
Open
Nobody has claimed this yet.
enhancement
I3
neofs-adm
neofs-cli
S4
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
neofs-admcurrently does not have default config path.- I would be nice to support multiple default paths -- we could install default system config in
/etc/whateverand allow each user to have it's own config in~/.config/neofs-cli.yml.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the configuration-loading entry points for neofs-cli and neofs-adm. Determine how default paths are currently handled, then verify that neofs-adm has a default and that both tools support system and per-user configuration paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100