Move fschain_autodeploy out of top level #1418

Closed
opened 2025-12-28 17:22:56 +00:00 by sami · 0 comments
Owner

Originally created by @roman-khimov on GitHub (May 20, 2025).

Originally assigned to: @End-rey on GitHub.

I'm always frustrated when:

  • we have a config that is true for all networks yet it has to be configured explicitly
  • we have a lot of top level configs without logical grouping

Describe the solution you'd like

  1. Create an fschain.disable_autodeploy with an inverse meaning, we use autodeploy by default, but don't if disable_autodeploy is 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).
  2. Make fschain_autodeploy default to true, but support it for one more release (simplifying transition).
  3. In subsequent release drop fschain_autodeploy completely.

Describe alternatives you've considered

Keeping things as is is not very convenient.

Additional context

#2423.

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: * we have a config that is `true` for all networks yet it has to be configured explicitly * we have a lot of top level configs without logical grouping ## Describe the solution you'd like 1. Create an `fschain.disable_autodeploy` with an inverse meaning, we use autodeploy by default, but don't if `disable_autodeploy` is 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). 2. Make `fschain_autodeploy` default to `true`, but support it for one more release (simplifying transition). 3. In subsequent release drop `fschain_autodeploy` completely. ## Describe alternatives you've considered Keeping things as is is not very convenient. ## Additional context #2423.
sami 2025-12-28 17:22:56 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1418
No description provided.