-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Implement set-channel-definitions
for ChannelConfigStore.
#16101
base: develop
Are you sure you want to change the base?
Conversation
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌1 Results
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌1 Results
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
Flakeguard SummaryRan new or updated tests between View Flaky Detector Details | Compare Changes Found Flaky Tests ❌1 Results
ArtifactsFor detailed logs of the failed tests, please refer to the artifact failed-test-results-with-logs.json. |
SetChannelDefinitionsConfig struct { | ||
// DefinitionsByChain is a map of chain selectors -> ChannelConfigStore addresses -> ChannelDefinitions to deploy. | ||
DefinitionsByChain map[uint64]map[string]ChannelDefinition // Use string for address because of future non-EVM chains. | ||
MCMSConfig *MCMSConfig |
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.
@akhilchainani @ecPablo is there a common, canonical configuration struct that can be used here?
ccip, keystone and streams are all defining their own
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 think we don't have one yet. But all the types look very similar, we should just pick one and move it to https://github.com/smartcontractkit/chainlink/blob/develop/deployment/common/types/types.go
@@ -116,4 +116,5 @@ vendor/* | |||
|
|||
*.wasm | |||
contracts/lcov.info | |||
contracts/out/ |
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.
Why do we need this?
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 the output directory for compiling contracts. If you want to have the compiled artifacts locally, they will be in that location and git will show them to you as uncommitted new files. I ignored it, so I can keep the artifacts without being bugged about them and without any risk to accidentally committing them.
SetChannelDefinitionsConfig struct { | ||
// DefinitionsByChain is a map of chain selectors -> ChannelConfigStore addresses -> ChannelDefinitions to deploy. | ||
DefinitionsByChain map[uint64]map[string]ChannelDefinition // Use string for address because of future non-EVM chains. | ||
MCMSConfig *MCMSConfig |
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 think we don't have one yet. But all the types look very similar, we should just pick one and move it to https://github.com/smartcontractkit/chainlink/blob/develop/deployment/common/types/types.go
|
@@ -44,6 +44,8 @@ const ( | |||
ExecutorAccessControllerAccount deployment.ContractType = "ExecutorAccessControllerAccount" | |||
CancellerAccessControllerAccount deployment.ContractType = "CancellerAccessControllerAccount" | |||
BypasserAccessControllerAccount deployment.ContractType = "BypasserAccessControllerAccount" | |||
// Data Streams contracts | |||
ChannelConfigStore deployment.ContractType = "ChannelConfigStore" |
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.
Should this be defined in this high level types? Or can it be kept in a data-streams type section?
@ro-tex should all or some changesets be organized into contract/version subdirectory? |
deployment/llo
todeployment/data-stream
in order to avoid confusion.setChannelDefinitions
method call on the ChannelConfigStore contract.Requires
Supports