GCP Region issue #1334

Activity

1. P4T12ICK commented on Feb 9, 2026

   

   P4T12ICK

   on Feb 9, 2026

   Collaborator

   More actions

   We just have a new release of Attack Range v5 including a UI and API. Can you try it again? thank you.
2. janderik commented on Jul 22, 2026

   

   janderik

   on Jul 22, 2026

   More actions

   A few suggestions for making the GCP instance lookup more robust in gcp_service.py:get_single_instance_public_ip:

   1. Add a null-check with a helpful error message:

   def get_single_instance_public_ip(self, name, zone):
       instance = self.compute.instances().get(
           project=self.project, zone=zone, instance=name
       ).execute()
   
       if not instance:
           raise RuntimeError(
               f"GCP instance '{name}' not found in zone '{zone}'. "
               "Verify the instance name and zone are correct in your config."
           )
   
       network_interfaces = instance.get('networkInterfaces', [])
       if not network_interfaces:
           raise RuntimeError(
               f"Instance '{name}' has no network interfaces. "
               "Check that the instance was created with a network interface."
           )
       # ... rest of IP extraction

   2. Add retry logic with exponential backoff for the GCP API call, since transient 429s/503s are common:

   import time
   
   def _get_instance_with_retry(self, name, zone, max_retries=3, base_delay=1.0):
       for attempt in range(max_retries):
           try:
               return self.compute.instances().get(
                   project=self.project, zone=zone, instance=name
               ).execute()
           except googleapiclient.errors.HttpError as e:
               if e.resp.status in (429, 500, 503) and attempt < max_retries - 1:
                   time.sleep(base_delay * (2 ** attempt))
                   continue
               raise

   3. Validate region/zone consistency in your config validation step — ensure the zone string matches the region prefix (e.g., us-central1-a starts with us-central1). This prevents confusing errors where the API returns empty results because the zone doesn't exist in the specified region.