Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] character “!” is not allowed in the secret name with connector mysql #2129

Open
tahub05 opened this issue Aug 1, 2024 · 0 comments · May be fixed by #2130
Open

[BUG] character “!” is not allowed in the secret name with connector mysql #2129

tahub05 opened this issue Aug 1, 2024 · 0 comments · May be fixed by #2130
Labels
bug Something isn't working

Comments

@tahub05
Copy link

tahub05 commented Aug 1, 2024

Describe the bug
When using the Amazon Athena MySQL connector, if "!" is included in the secret name of Secrets Manager used when connecting to the database, the connection will fail.

To Reproduce
Steps to reproduce the behavior:

  1. Integrate Secrets Manager with Amazon RDS, and manage authentication information with Secrets Manager. At this time, the name of the secret is “rds! cluster-xxxxxxxxxx”.
  2. Deploy a Lambda function using the Athena MySQL connector.
  3. Create an Athena data source and use that Lambda function to connect to the data source.
  4. cannot connect to the database and an error occurs.

Expected behavior
The connection to the database succeeds even if “!” is included in the secret name

Screenshots / Exceptions / Errors
WrongArgumentException: Malformed database URL, failed to parse the connection string near '${rds!cluster-xxxxxxxxxx}'.

Connector Details (please complete the following information):

  • Version: 2024.25.1
  • Name: mysql
@tahub05 tahub05 added the bug Something isn't working label Aug 1, 2024
@tahub05 tahub05 linked a pull request Aug 1, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant