-
Notifications
You must be signed in to change notification settings - Fork 40
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: deploy multiple op l2s #20
Conversation
enable multi l2s
Co-authored-by: Barnabas Busa <[email protected]> Signed-off-by: Tedi Mitiku <[email protected]>
Could you please revert to use |
Can you please rebase over latest main branch? |
Signed-off-by: Tedi Mitiku <[email protected]>
|
||
Args: | ||
args(yaml): Configures other aspects of the environment. | ||
args(json): Configures other aspects of the environment. |
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.
currently, our package indexer only picks up json
(you can still pass it in as yaml but starlark converts it to json) so in order for the package to show up in package catalog, has to be set to json instead of yaml. I can update package indexer to support yaml type as well
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.
which package indexer?
Enables configuring and deploying multiple l2s on top of the same l1. The biggest difference is splitting up contract deployment to deploy factory contract in a separate
run_sh
once.example config: