Skip to content
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

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

Conversation

EasterTheBunny
Copy link
Contributor

@EasterTheBunny EasterTheBunny commented Dec 10, 2024

This commit provides using an existing env var CL_CHAIN_DEFAULTS 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.

CCIP-4395

// 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 != "" {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

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

Copy link
Contributor

github-actions bot commented Dec 10, 2024

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@EasterTheBunny EasterTheBunny force-pushed the etb/toml-custom-fallback branch from 1d753ac to 436023c Compare December 11, 2024 16:59
@EasterTheBunny EasterTheBunny force-pushed the etb/toml-custom-fallback branch 2 times, most recently from a449414 to f57243d Compare December 13, 2024 16:20
This commit provides using an existing env var `CL_CHAIN_DEFAULTS` 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.
@EasterTheBunny EasterTheBunny force-pushed the etb/toml-custom-fallback branch from f57243d to 4515f8a Compare December 13, 2024 16:21
@EasterTheBunny EasterTheBunny force-pushed the etb/toml-custom-fallback branch from ba58f5c to 2a8f287 Compare December 13, 2024 17:05
mateusz-sekara
mateusz-sekara previously approved these changes Dec 13, 2024
core/chains/evm/config/toml/defaults.go Outdated Show resolved Hide resolved
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incidental?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup. I don't know why that is there. I can remove it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Now I'm not sure what this is. It must be incidental because I added a new .txtar file to handle the new test case. I don't think I can remove it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens if you revert this file? I thought it would only update from a manual command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants