-
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
feat: ds configurator Changesets #16713
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 ✅ |
a8de9e4
to
9eb250b
Compare
Since we currently have 6 contract types - does it make sense to organize them into their own package? I think this organization would make sense when we start having future contract versions as well that their implementation details can be tucked away in a package. I started doing this but can keep everything flat if we don't want to do this |
deployment/data-streams/changeset/call_configurator_set_staging_config.go
Show resolved
Hide resolved
deployment/data-streams/changeset/call_configurator_set_staging_config.go
Show resolved
Hide resolved
deployment/data-streams/changeset/call_configurator_set_production_config.go
Outdated
Show resolved
Hide resolved
deployment/data-streams/changeset/call_configurator_set_staging_config.go
Outdated
Show resolved
Hide resolved
deployment/data-streams/changeset/call_configurator_promote_staging_config.go
Outdated
Show resolved
Hide resolved
commonChangesets.Configure( | ||
DeployConfiguratorChangeset, | ||
DeployConfiguratorConfig{ | ||
ChainsToDeploy: []uint64{chainSelector}, |
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.
set MCMS config? Or come back and do this later?
1103d37
to
50a1fd3
Compare
|
Description
Add Configurator support for data streams deployment module
References