-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new config adapter #6925
new config adapter #6925
Conversation
I see that you haven't updated any CHANGELOG files. Would it make sense to do so? |
a28aeed
to
c7473ec
Compare
38c61f2
to
11d3501
Compare
c2a0681
to
0943de1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few more comments/questions. Apologies if they don't make sense :)
0943de1
to
ea18ef6
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In general this PR looks good to me!
45a2057
to
1949c46
Compare
4916351
to
a60f48a
Compare
8882a7c
to
3938cbe
Compare
e3d1449
to
b0728b9
Compare
b0728b9
to
0e1cb34
Compare
if n.Name == nil { | ||
err = multierr.Append(err, v2.ErrMissing{Name: "Name", Msg: "required for all nodes"}) | ||
} else if *n.Name == "" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What are the different scenarios where this could be nil or empty?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just user input, so when a user omits them or enters empty string.
# | ||
# Because of the complications with advisory locks, Chainlink nodes with v1.1.0 and later support a new `lease` locking mode. This mode might become the default in future. The `lease` locking mode works using the following process: | ||
# Because of the complications with advisory locks, Chainlink nodes with v2.0 and later only support `lease` locking mode. The `lease` locking mode works using the following process: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't remove advisory locking completely, I think we just want to make lease
the new default.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you change your mind, or did I misunderstand? https://app.shortcut.com/chainlinklabs/story/45329/deprecate-database-locking-mode-advisory
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The high-level structure looks good to me. I can't speak for specific config fields, though.
Given that this is not going to be in prod just yet, I don't see a large risk in merging, which will unblock a few smaller efforts that can be worked on in parallel.
Towards https://app.shortcut.com/chainlinklabs/story/33615/create-new-implementation-of-chainscopedconfig-generalconfig-interfaces-that-sources-config-from-a-config-toml-file
This PR begins adapting the new toml config input to the legacy
ChainScopedConfig
/GeneralConfig
interfaces.Supporting PRs