Add testrecipient back to infra and CoreDeployer #3274
Assignees
Comments
aroralanuk
added a commit
that referenced
this issue
Feb 19, 2024
### Description - Added `TestRecipientDeployer` to the core deployer because most of the times, the TestRecipient is required right after core deployment and it's very lightweight. The TestRecipient deployment is also an unnecessary extra step in the runbook. - Put it back in infra/deploy which gives the deployer the option to deploy it separately. ### Drive-by changes None ### Related issues - fixes #3274 ### Backward compatibility Yes ### Testing Fork tests
ltyu
pushed a commit
to ltyu/hyperlane-monorepo
that referenced
this issue
Mar 13, 2024
) ### Description - Added `TestRecipientDeployer` to the core deployer because most of the times, the TestRecipient is required right after core deployment and it's very lightweight. The TestRecipient deployment is also an unnecessary extra step in the runbook. - Put it back in infra/deploy which gives the deployer the option to deploy it separately. ### Drive-by changes None ### Related issues - fixes hyperlane-xyz#3274 ### Backward compatibility Yes ### Testing Fork tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
We removed the
testrecipientmodule from infra deploy recently. The TestRecipient deployment is also an unnecessary extra step in the runbook.Solution
We should add it back and also have the
CoreDeployeruse theTestRecipientDeployerinternally for one fewer default entrypoints.It is still useful to have separate entrypoints for the
testrecipientdeploy to enable contexts with different ISM configurations.The text was updated successfully, but these errors were encountered: