Setting disable_execute_api_endpoint to false should leavee Execute API endpoint enabled.

[dgholz]

Description

Recreating #128, since it went stale.

We'd still like this to work, our motivations are unchanged:

For our use case, we'd like to leave the default endpoint available when we have a domain configured.

We have an externally-facing API that clients request jobs through. Their requests get forwarded onto a Step Function to perform the work. To allow the clients to view the progress of their work, the Step Functions send updates to the API with status messages (stored in DynamoDB) that the clients can then retrieve. We use API Gateway: Invoke tasks from the Step Function to access the API Gateway, which require an execute-api endpoint parameter to specify which API Gateway to invoke. We prefer sending our own status messages, so they are understandable to the clients, rather than the description of the Step Function execution (which sometimes are harder to map to user intentions).

We're happy to leave the default endpoint enabled: even though it would allow clients to directly invoke the API Gateway, we don't publish it for them to use & restrict access to the routes with IAM authentication. We prefer clients to use the domain name, in case we replace the API Gateway in the future & its ID changes. If API Gateway: Invoke tasks could use the domain name instead of the execute-api endpoint, we'd happily switch.

I guess we could configure two APIs: one for clients to use & another for our Step Functions to call. Though we would have to configure the Step Functions to look up the appropriate API Gateway to use, instead of passing it through from the API Gateway's context.

[dgholz]

I make #130 to resolve this issue, but it also went stale. Happy to re-create it as well, and take on any suggestions to improve the testing.