-
Notifications
You must be signed in to change notification settings - Fork 91
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: op stack integration #418
Conversation
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.
Cool, thanks for checking this. By the way, I added a new monitor for OP rollups to check if L2 blocks are finalized after some time. https://github.com/0xPolygon/kurtosis-cdk/actions/runs/12197982923/job/34028778002?pr=418 |
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've tested the deployment by setting "deploy_optimism_rollup": True,
and it seems to be working without issues. But when testing with different combinations of DEFAULT_DEPLOYMENT_STAGES input, there were some combinations which resulted in errors during deployment - this may not be the intended way to use it, so just raising for awareness.
Status
v1.2.0
and migrate to this version to merge the PR.Description
The goal is to add a new option to deploy an OP stack rollup inside our package.
To deploy the default OP stack rollup, you can use:
You can also customize the rollup:
References (if applicable)