-
Notifications
You must be signed in to change notification settings - Fork 62
Open
Description
We ran into this problem in a project that relies only on ApiGatewayClient.
<!-- AWS -->
<dependency>
<groupId>io.quarkiverse.amazonservices</groupId>
<artifactId>quarkus-amazon-apigateway</artifactId>
</dependency>
<dependency>
<groupId>software.amazon.awssdk</groupId>
<artifactId>url-connection-client</artifactId>
</dependency>
In this scenario no devservices are started
We get it to start by requesting additional services as detailed in the dev services docs, like:
quarkus.aws.devservices.localstack.additional-services."redshift".enabled=true
In this case the localstack gets started but refuses our apigateway requests, I assume it's because the service was not propperly started.
This also happens if we add a devservice dependency, e.g.: quarkus-amazon-devservices-s3
We can manually achieve the availability by starting localstack with docker-compose and pointing to it
I've attached a sample project for reference of the use case.
Thanks!
Metadata
Metadata
Assignees
Labels
No labels