Validating REGION against hardcoded region names instead of dynamic provider-specific regions
When attempting to create subprojects, the
storage_location parameter is restricted to a hardcoded list of values (GCP values?).
These values are hardcoded here, in
When attempting to pass an AWS-specific region, this is the error code received:
 [seismic-store-service] The storage_location body field US-EAST-1 is not valid. It must be one of ASIA, EU, US, NORTHAMERICA-NORTHEAST1, US-CENTRAL1, US-EAST1, US-EAST4, US-WEST1, SOUTHAMERICA-EAST1, EUROPE-WEST1, EUROPE-WEST2, EUROPE-WEST3, EUROPE-WEST4, ASIA-EAST1, ASIA-NORTHEAST1, ASIA-SOUTH1, ASIA-SOUTHEAST1, AUSTRALIA-SOUTHEAST1
Subproject creation should validate the user-provided region against cloud provider's regions dynamically.
This might already be addressed in @DiegoMolteni's upcoming updates to make the Seismic service more abstracted and generic. If not, can we work to abstract
parser.ts to have cloud provider specific implementations?