fix: handling for l1 deployment to remote network

0xPolygon · Jun 10, 2024 · 8dbfba8 · 8dbfba8
1 parent 6e1650c
commit 8dbfba8
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 3 deletions.
diff --git a/cdk_bridge_infra.star b/cdk_bridge_infra.star
@@ -46,9 +46,10 @@ def run(plan, args):
     )
     zkevm_bridge_package.start_bridge_ui(plan, args, bridge_ui_config_artifact)
 
-    # Start the bridge UI reverse proxy.
-    proxy_config_artifact = create_reverse_proxy_config_artifact(plan, args)
-    zkevm_bridge_package.start_reverse_proxy(plan, args, proxy_config_artifact)
+    # Start the bridge UI reverse proxy. This is only relevant / needed if we have a fake l1
+    if args["deploy_l1"]:
+        proxy_config_artifact = create_reverse_proxy_config_artifact(plan, args)
+        zkevm_bridge_package.start_reverse_proxy(plan, args, proxy_config_artifact)
 
 
 def create_agglayer_config_artifact(plan, args, contract_setup_addresses, db_configs):

diff --git a/main.star b/main.star
@@ -102,6 +102,7 @@ def run(
     # Deploy cdk/bridge infrastructure.
     if deploy_cdk_bridge_infra:
         plan.print("Deploying cdk/bridge infrastructure")
+        args["deploy_l1"] = deploy_l1
         import_module(cdk_bridge_infra_package).run(plan, args)
     else:
         plan.print("Skipping the deployment of cdk/bridge infrastructure")