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
Although I configured Maven to generate and pass a random socket port to start DynamoDB on, that port number is ignored. Instead the plugin uses port 10101.
I do not know where port 10101 is defined. Even if I did, I'd like the plugin to ignore it and to start Dynamo with the random port generated in the pom.
The plugin uses the correct random port when trying to connect to Dynamo (to create a table). But that connect fails because Dynamo is listening on port 10101.
[DEBUG] Configuring mojo 'com.jcabi:jcabi-dynamodb-maven-plugin:0.8:create-tables' with basic configurator -->
[DEBUG] (f) endpoint = http://localhost
[DEBUG] (f) key = AWS-Key
[DEBUG] (f) port = 10101
[DEBUG] (f) secret = AWS-Secret
[DEBUG] (s) skip = false
[DEBUG] (f) tables = [~/_dev/foo-proj/src/test/resources/dynamo/my-table.json]
[DEBUG] -- end configuration --
[INFO] >> Initializing DynamoDB Local with the following configuration:
[INFO] >> Port: 55569
[INFO] >> InMemory: false
[INFO] >> DbPath: null
[INFO] >> SharedDb: false
[INFO] >> shouldDelayTransientStatuses: false
[INFO] >> CorsParams: *
It would be ideal if the plugin ignored external Dynamo config and overrode it with config settings defined in the pom.xml.
The text was updated successfully, but these errors were encountered:
I ran into a problem with this plugin.
Although I configured Maven to generate and pass a random socket port to start DynamoDB on, that port number is ignored. Instead the plugin uses port 10101.
I do not know where port 10101 is defined. Even if I did, I'd like the plugin to ignore it and to start Dynamo with the random port generated in the pom.
The plugin uses the correct random port when trying to connect to Dynamo (to create a table). But that connect fails because Dynamo is listening on port 10101.
It would be ideal if the plugin ignored external Dynamo config and overrode it with config settings defined in the pom.xml.
The text was updated successfully, but these errors were encountered: