Skip to content
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

op-deployer: Safety and validation improvements #12993

Merged
merged 1 commit into from
Nov 20, 2024

Conversation

mslipper
Copy link
Collaborator

  • Enables support for deploying tagged versions against new chains, but behind a huge warning that requires user input to bypass. Since our tagged release versions do not contain all implementations, using op-deployer in this way will deploy contracts that haven't been governance approved. Since this workflow is useful for development but bad for prod, I've added support for it but users have to bypass a large warning that describes the risks.
  • Validates the hashes of tagged version artifacts after downloading them. This prevents users from downloading tampered versions of the artifacts from GCS.

@mslipper mslipper requested a review from a team as a code owner November 19, 2024 23:55
@mslipper mslipper requested review from mds1 and blmalone November 19, 2024 23:55
@mslipper mslipper force-pushed the feat/deployer-validate-hash branch 3 times, most recently from 18a92fc to 64cf4fd Compare November 20, 2024 00:49
- Enables support for deploying tagged versions against new chains, but behind a huge warning that requires user input to bypass. Since our tagged release versions do not contain all implementations, using op-deployer in this way will deploy contracts that haven't been governance approved. Since this workflow is useful for development but bad for prod, I've added support for it but users have to bypass a large warning that describes the risks.
- Validates the hashes of tagged version artifacts after downloading them. This prevents users from downloading tampered versions of the artifacts from GCS.
@mslipper mslipper force-pushed the feat/deployer-validate-hash branch from 64cf4fd to a54047a Compare November 20, 2024 00:57
Copy link
Contributor

@blmalone blmalone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice!

@mslipper mslipper added this pull request to the merge queue Nov 20, 2024
Merged via the queue into develop with commit b05ec5a Nov 20, 2024
49 checks passed
@mslipper mslipper deleted the feat/deployer-validate-hash branch November 20, 2024 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants