Deploy Terraform configs in CI #2994
Assignees
Labels
A-devops
Area: Devops. E.g. CI / build systems
Comments
PhilWindle
added a commit
that referenced
this issue
Dec 1, 2023
Closes #2994 Closes #2998 Closes #2999 Closes #3130 - Create a pipeline to deploy not just our versioned releases, but all merges to `master` to Dockerhub, under `aztec-dev` tag - Run terraforms to deploy 2 aztec node instances, 2 p2p bootstrap nodes + a faucet - Deploys L1 contracts to our new mainnet fork. # Checklist: Remove the checklist to signal you've completed it. Enable auto-merge if the PR is ready to merge. - [ ] If the pull request requires a cryptography review (e.g. cryptographic algorithm implementations) I have added the 'crypto' tag. - [ ] I have reviewed my diff in github, line by line and removed unexpected formatting changes, testing logs, or commented-out code. - [ ] Every change is related to the PR description. - [ ] I have [linked](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) this pull request to relevant issues (if any exist). --------- Co-authored-by: PhilWindle <60546371+PhilWindle@users.noreply.github.com> Co-authored-by: PhilWindle <philip.windle@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently just validate any terraforms that are present on a project's directory.
As part of devnet deployment, we should add a job that applies terraform files when merged to
masterbranchThe text was updated successfully, but these errors were encountered: