fix: warp route checker (#4810)
### Description - Updates the .registryrc, which we will need to update when we add new warp route configs to infra, otherwise we'll get ``` Checking warp route WBTC/eclipsemainnet-ethereum... Error checking warp route USDT/eclipsemainnet-ethereum-solanamainnet: Error: Warp route config for USDT/eclipsemainnet-ethereum-solanamainnet not found in registry Error checking warp route WBTC/eclipsemainnet-ethereum: Error: Warp route config for WBTC/eclipsemainnet-ethereum not found in registry Failed to check warp routes: USDT/eclipsemainnet-ethereum-solanamainnet, WBTC/eclipsemainnet-ethereum ``` - Uses the `Always` imagePullPolicy (https://kubernetes.io/docs/concepts/containers/images/#image-pull-policy) to ensure we always use latest main - A consequence of removing Lumia addresses from the registry in https://github.com/hyperlane-xyz/hyperlane-registry/pull/348 is that this broke checking of the Lumia warp route. I manually specify the required addresses here now. - Also needed to explicitly specify the proxyAdmin ownership Definitely some opportunities for improvement with the warp route deploy flow ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->pull/4770/head
parent
ffbc13cc58
commit
fbce40f891
@ -1 +1 @@ |
|||||||
302be4817c063629cec70c0b02322b250df71122 |
14836804e543a64cd3747cd6bbea6e245b6353b1 |
||||||
|
Loading…
Reference in new issue