You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the local gateways have paths that include a hardcoded path key. This hardcoded value should be replaced with a random uuid, which is the current configuration for AWS and GCP gateways. Slack discussion here.
For example, the local HTTP gateway path is defined as:
Note that as of #1869, implementing this will require the E2E test to capture the non-hardcoded gateway URLs during local deployment because currently DEFAULT_PATH_KEY is used:
Currently, the local gateways have paths that include a hardcoded path key. This hardcoded value should be replaced with a random uuid, which is the current configuration for AWS and GCP gateways. Slack discussion here.
For example, the local HTTP gateway path is defined as:
airnode/packages/airnode-node/src/workers/local-gateways/server.ts
Line 126 in 3472e6b
with the hardcoded value from here:
airnode/packages/airnode-node/src/workers/local-gateways/server.ts
Line 26 in 3472e6b
In contrast, AWS and GCP use
random_uuid
:airnode/packages/airnode-deployer/terraform/aws/variables.tf
Line 10 in 624b737
The text was updated successfully, but these errors were encountered: