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

Child DB Security Key Spam #119

Open
MKRazz opened this issue Feb 28, 2022 · 1 comment
Open

Child DB Security Key Spam #119

MKRazz opened this issue Feb 28, 2022 · 1 comment

Comments

@MKRazz
Copy link

MKRazz commented Feb 28, 2022

If you run a command while using a child database, it will create a new key and leave it there, so you eventually end up with tons of keys on the parent database. Could these keys be deleted after the command is done running?

@ryancausey
Copy link

I'm no TS expert, but looking at the code it appears to create a child key every time the child DB is accessed. I think a better approach would be to use scoped keys. Fauna schema migrate already needs access to an admin key for the parent database in order to create child ones, so it shouldn't need to create a new key.

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

2 participants