feat: create deploy-rollup-contracts.yml #16549
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
db8884c to
103df70
Compare
just-mitch
changed the title
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
103df70 to
0f5a5e6
Compare
This was referenced Aug 24, 2025
just-mitch
force-pushed
the
08-22-mitch_tmnt-165-create-deploy-eth-devnetyml
branch
from
5973cff to
b10a81f
Compare
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
0f5a5e6 to
ed3868b
Compare
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
ed3868b to
4625b9d
Compare
just-mitch
force-pushed
the
08-22-mitch_tmnt-165-create-deploy-eth-devnetyml
branch
2 times, most recently
from
8db0546 to
4709157
Compare
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
4625b9d to
2f88902
Compare
just-mitch
force-pushed
the
08-22-mitch_tmnt-165-create-deploy-eth-devnetyml
branch
from
4709157 to
4900419
Compare
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
2f88902 to
9fab426
Compare
just-mitch
force-pushed
the
08-22-mitch_tmnt-165-create-deploy-eth-devnetyml
branch
from
4900419 to
c3a1cd5
Compare
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
9fab426 to
1c7563b
Compare
alexghr
approved these changes
Aug 28, 2025
Contributor
alexghr
left a comment
alexghr
left a comment
There was a problem hiding this comment.
Looks great but I think Github will struggle with the deployment workflow if it's got this many input parameters
| required: true | ||
|
|
||
| workflow_dispatch: | ||
| inputs: |
Contributor
There was a problem hiding this comment.
I think this will hit the '10 inputs hard limit' on workflow_dispatch
Collaborator
Author
There was a problem hiding this comment.
Yep I'll remove them in a stacked PR 👍
Base automatically changed from
08-22-mitch_tmnt-165-create-deploy-eth-devnetyml
to
next
August 28, 2025 18:17
just-mitch
force-pushed
the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
from
1c7563b to
79f0f2b
Compare
just-mitch
deleted the
08-23-mitch_tmnt-166-create-deploy-rollup-contractsyml
branch
This was referenced Aug 29, 2025
ludamad
pushed a commit
that referenced
this pull request
Dec 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a new GitHub workflow and Terraform configuration for deploying Aztec rollup contracts to Kubernetes clusters. The implementation includes:
deploy-rollup-contracts.ymlthat can be triggered manually or called from other workflowsspartan/terraform/deploy-rollup-contracts/to handle the deployment processThe workflow allows customization of various Aztec parameters like slot duration, epoch duration, committee size, and other protocol-specific settings. It also supports optional features like sponsored FPC and real verifier deployment.