-
Notifications
You must be signed in to change notification settings - Fork 0
feat: deploy custom topology mcms [CLD-2766] #100
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
Changes from all commits
7b2ded2
55ea3be
f9aab1d
ed8ab5c
44c087b
5d0d941
b05953d
05e8c69
0961740
0cf7ac3
1bad648
00f1923
08f25ce
41dbbe3
21e456e
c112b33
9e4e51b
dd1c08b
64cd08b
4fce639
2e0c579
aea9450
0594dd9
d9fd9f2
f91be67
d95268a
215e6d9
bac6cf5
99a9ee1
1896f69
53e0365
6180e35
6c772fd
9838c45
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -2,22 +2,22 @@ package operations | |
|
|
||
| import ( | ||
| "github.com/Masterminds/semver/v3" | ||
| "github.com/ethereum/go-ethereum/accounts/abi/bind/v2" | ||
| "github.com/ethereum/go-ethereum/accounts/abi/bind" | ||
| "github.com/ethereum/go-ethereum/common" | ||
| "github.com/ethereum/go-ethereum/core/types" | ||
|
|
||
| mcmscontracts "github.com/smartcontractkit/chainlink-deployments-framework/engine/cld/contracts/mcms" | ||
| "github.com/smartcontractkit/mcms/sdk/evm/bindings" | ||
|
|
||
| "github.com/smartcontractkit/cld-changesets/legacy/mcms/internal/family/evm/oputil" | ||
| "github.com/smartcontractkit/cld-changesets/mcms/evm/operations" | ||
| ) | ||
|
ecPablo marked this conversation as resolved.
|
||
|
|
||
| type OpGrantRoleInput struct { | ||
| Account common.Address `json:"account"` | ||
| RoleID [32]byte `json:"roleID"` | ||
| } | ||
|
|
||
| var OpGrantRole = oputil.NewEVMCallOperation( | ||
| var OpGrantRole = operations.NewEVMCallOperation( | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I wonder if we need to move
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes I just did that in this PR, the
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually i meant should we keep
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. For the mcms specific ones, since we'll still be using the mcms lib for them I think most of them with the execption of the deploy won't be using the ops gen tool right? So maybe worth keeping it in the non-legacy folder?
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. for deploy , currently we are using ops gen tool but for the others, i thought we will dedicate everything else to mcms sdk instead and i thought if we are using the mcms sdk then we will not be using
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Ah I see now, you're right. Let me move the entire |
||
| "evm-timelock-grant-role", | ||
| semver.MustParse("1.0.0"), | ||
| "Grants specified role to the ManyChainMultiSig contract on the EVM Timelock contract", | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.