-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Custom Fallback TOML Config #15617
base: develop
Are you sure you want to change the base?
Custom Fallback TOML Config #15617
Conversation
I see you updated files related to
|
// fallback.toml(defaults dir) <- fallback.toml(env CL_CHAIN_FALLBACK) <- ChainSpecific.toml(env CL_CHAIN_DEFAULTS) | ||
// | ||
// the custom fallback gets processed and overrides the default fallback | ||
if path := env.CustomFallback.Get(); path != "" { |
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.
can we lock this in with a testscripts test like in https://github.com/smartcontractkit/chainlink/pull/14090/files#diff-ea10429fdb1fbc100e3d8082e39e6d40a12f82b48c1f37ab9158b6c3c0e44d81 ?
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.
Good idea. I'll add that
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
This commit provides setting a new env var `CL_CHAIN_FALLBACK` as a path to a custom `fallback.toml`. This allows plugins to define their own set of fallback options apart from the core node which override the default fallback options.
1d753ac
to
436023c
Compare
This commit provides setting a new env var
CL_CHAIN_FALLBACK
as a path to a customfallback.toml
. This allows plugins to define their own set of fallback options apart from the core node which override the default fallback options.CCIP-4395