mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Move fschain_autodeploy out of top level #1418
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#1418
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @roman-khimov on GitHub (May 20, 2025).
Originally assigned to: @End-rey on GitHub.
Is your feature request related to a problem? Please describe.
I'm always frustrated when:
truefor all networks yet it has to be configured explicitlyDescribe the solution you'd like
fschain.disable_autodeploywith an inverse meaning, we use autodeploy by default, but don't ifdisable_autodeployis true. This config shouldn't be used normally, only in case of emergency/node failing to work with autodeploy for whatever reason (although practically it's super-stable now).fschain_autodeploydefault totrue, but support it for one more release (simplifying transition).fschain_autodeploycompletely.Describe alternatives you've considered
Keeping things as is is not very convenient.
Additional context
#2423.