ci: fix including arb one in retryable monitor

OffchainLabs · Aug 21, 2024 · 0f4e914 · 0f4e914
1 parent 459263b
commit 0f4e914
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/workflows/monitoring.yml b/.github/workflows/monitoring.yml
@@ -53,7 +53,7 @@ jobs:
     - name: Generate chains JSON
       run: yarn workspace arb-token-bridge-ui ${{ steps.config.outputs.generate_command }}
       env:
-        BATCH_POSTER_MONITORING: ${{ inputs.monitor == 'batch-poster' }}
+        INCLUDE_ARB_ONE_AS_CORE_CHAIN: ${{ inputs.monitor != 'retryable' }}
 
     - name: Copy chains JSON to Arbitrum Monitoring
       run: cp ./packages/arb-token-bridge-ui/public/${{ steps.config.outputs.config_file }} ./arbitrum-monitoring/packages/${{ inputs.monitor }}-monitor/config.json

diff --git a/packages/arb-token-bridge-ui/scripts/generateCoreChainsToMonitor.ts b/packages/arb-token-bridge-ui/scripts/generateCoreChainsToMonitor.ts
@@ -24,7 +24,7 @@ async function generateCoreChainsToMonitor() {
   }
 
   // don't need to monitor arbOne chain in case of retryable-monitoring
-  const chains = process.env.BATCH_POSTER_MONITORING
+  const chains = process.env.INCLUDE_ARB_ONE_AS_CORE_CHAIN
     ? [arbOneChain, novaChain]
     : [novaChain]