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

Can't connect postgresql RDS via Secret Manager seems JSON serialize error #5132

Open
zshnb opened this issue Nov 26, 2024 · 4 comments
Open
Labels
bug We can reproduce the issue and confirmed it is a bug.

Comments

@zshnb
Copy link

zshnb commented Nov 26, 2024

Describe the bug
I setup aws connection in toolkit, then try connect via secret manager, when I test connection I got error
Unexpected character ('G' (code 71)): Expected space separating root-level values at [Source: REDACTED (StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION disabled)
To reproduce

  1. open DataSource panel
  2. fill host, choose secret manager auth
  3. select credentials and region
  4. fill secret name/arn
  5. test connection

Expected behavior
connect success

Screenshots
image

Your Environment

  • OS: MacOS
  • JetBrains product: DataGrip 2024.2
  • JetBrains product version: 2024.2
  • AWS Toolkit version: latest
  • SAM CLI version: aws cli 2.22.5
  • JVM/Python version: 17

Additional context

@zshnb zshnb added the bug We can reproduce the issue and confirmed it is a bug. label Nov 26, 2024
@yogevyuval
Copy link

I think by the code that maybe the plugin expects the secret to be in a json format with more fields (hence the "use the url and port from the secret"), but this is not documented anywhere.

Try changing your secret to a json with "username" and "password" keys

@zshnb
Copy link
Author

zshnb commented Dec 4, 2024

does there has any docs about it?

@yogevyuval
Copy link

does there has any docs about it?

None at all :(
It just worked for me though. {"username": "x", "password": "y"}

did you get it to work?

@zshnb
Copy link
Author

zshnb commented Dec 6, 2024

I will try it, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug.
Projects
None yet
Development

No branches or pull requests

2 participants