Closed mati999q closed 7 months ago
Hi @mati999q thanks for reporting the issues, I'm able to reproduce the bug1, but the bug2 is quite specific, you might missing AWS_REGION
environmental variable, but I can supply all aws s3 calls with AWS REGION
.
Bug 1
Describe the bug After the latest update, when initialising a new CQL Replicator env, the glue connection is made with the naming convention cql-replicator-{uuid}$DEFAULT_ENV
The glue job which is created then appends the $DEFAULT_ENV to the end of this name, and tries to use it as a connection. This results in an error
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
CQL Replicator should be able to provide a working environment when first created.
Screenshots
Additional context Difficult when explaining how to use the tool, to add one more thing to explain and change / I managed to fix by removing an extra $DEFAULT_ENV when creating glue job
Bug 2
Describe the bug When creating bucket in s3, region flag is not present by default resulting in an errors
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
CQL Replicator should be able to provide a working environment when first created.
Additional context Difficult when explaining how to use the tool, to add one more thing to explain and change / I managed to fix by adding in a --region $AWS_REGION flag inside the aws s3 mb command, though wish it was already there when upgrading to new version