chore: re-enforce a whitelist policy in the RC relayer (#4032)

### Description

<!--
What's included in this PR?
-->

### 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/4033/head
Daniel Savu 5 months ago committed by GitHub
parent f1fe882e3b
commit b54c14cd31
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
  1. 4
      typescript/infra/config/environments/mainnet3/agent.ts

@ -287,9 +287,7 @@ const releaseCandidate: RootAgentConfig = {
repo, repo,
tag: '0d12ff3-20240620-173353', tag: '0d12ff3-20240620-173353',
}, },
// We're temporarily (ab)using the RC relayer as a way to increase whitelist: releaseCandidateHelloworldMatchingList,
// message throughput.
// whitelist: releaseCandidateHelloworldMatchingList,
gasPaymentEnforcement, gasPaymentEnforcement,
metricAppContexts, metricAppContexts,
resources: relayerResources, resources: relayerResources,

Loading…
Cancel
Save