-
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
Keystone e2e test #15182
base: develop
Are you sure you want to change the base?
Keystone e2e test #15182
Conversation
# Conflicts: # integration-tests/go.mod
48a0339
to
c92fea5
Compare
7237990
to
49b858e
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.
Please don't commit binaries
ExistingHashedCapabilitiesIDs [][32]byte | ||
} | ||
|
||
func Deploy(sc *seth.Client) (*CapabilitiesRegistryInstance, error) { |
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 not reuse, extend and unify on the work in deployment/keystone?
ccip is doing something similiar -- all deployment logic is unified and they have a devenv
for integration tests
Follow-ups
build
step instead of re-creating it.