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

Add the possibility to remove a file uploaded to a secret #628

Open
oleastre opened this issue Jul 25, 2024 · 1 comment
Open

Add the possibility to remove a file uploaded to a secret #628

oleastre opened this issue Jul 25, 2024 · 1 comment

Comments

@oleastre
Copy link

I'm trying to manage some generated files in Keeper.
With the current implementation:

  • I use ksm secret upload with a file
  • I can get the secret and file with ksm secret get and ksm secret download
  • If I try to update the secret fileRef field, it only removes the reference to the file, the file is still listed when I do a ksm secret get

What I would expect is either a specific command to remove a file (similar to ksm secret upload and ksm secret download), a specific ksm secret update parameter to delete a file, or have the ksm secret update --field-json fileRef=... cleanup not referenced files.

@flybyray
Copy link

Thanks for that ticket. I need to test this in my evaluation too.

A KSM demo showed secret rotation. I would assume exactly for such rotation such basic operations to replace file attachments should be available too. Did you checked if this stuff with KSM Gateway would allow rotating file attachments?

Managing clustered databases where nodes communicate via certificates I would like to have several different types of certificates assigned per instance per record. And of course I need selective rotation for those certificates attached as files too.

I would expect that basic "CRUD" operations should be possible manually/interactive with KSM Cli but also with the KSM secret rotation. Switching the tooling (Commander) only for certain tasks would introduce a lot of additional pain.

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