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

AWS Secret names with slash '/' #29

Closed
BhuviTheDataGuy opened this issue Jul 17, 2021 · 3 comments
Closed

AWS Secret names with slash '/' #29

BhuviTheDataGuy opened this issue Jul 17, 2021 · 3 comments

Comments

@BhuviTheDataGuy
Copy link

I have a secret in AWS Secret manager with this name dev/debezium/mysql/testservice/password

I tried to use this name in my source connector.

 "database.password": "${aws:dev/debezium/mysql/testservice/password:mysql_pass}",

In my worker properties, the file.dir=/etc/kafka

And the error I got is,

java.nio.file.AccessDeniedException: /etc/kafka/dev

But when I created empty folders in the same SECRET NAME, then its resolved.

mkdir -p /etc/kafka/dev/debezium/mysql/testservice/password
@xphir
Copy link

xphir commented Nov 10, 2021

I know the fact it makes an internal file and doesn't let you disable this functionality is an issue, the following is a workaround.

But for others having the same issue, the workaround is to make sure your specified file.dir in the config provider has the correct permissions. For example if you gave the following config.providers.aws.param.file.dir=/connector-files/aws then make sure you have the permission to write within the /connector-files/aws directory.

As long as you have the correct permissions within that folder you have specified, then it will create the full path in the background and it wont produce an error.

@davidsloan
Copy link
Contributor

#19 (no longer storing secret files by path) and #50 (toggling on/off storing secrets using file.write property) should resolve this problem. Both will be included in the next release.

@davidsloan
Copy link
Contributor

davidsloan commented Nov 1, 2023

This is released in 2.3.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants