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

Would it be possible to add the name of who changed the settings ? #43

Closed
arnaudbuchholz-sap opened this issue Oct 4, 2023 · 5 comments

Comments

@arnaudbuchholz-sap
Copy link

Among the amazing features of the tool, I would like to have the name of who changed the settings when looking back in time.

NOTE: gcloud info gives the account name ;-)

image

@hawser86
Copy link
Contributor

hawser86 commented Oct 9, 2023

Thanks for the idea.

The Secret Editor does not save backups, but only reads them and provides a UI to restore secrets based on the backups. Backups are saved by the secret-backup-operator, which saves the backups regardless the tool you use to modify the secret (Secret Editor, gap-cli, k9s, etc.).

At first this operator needs to be extended to save the username, as well. When it is done, Secret Editor can be extended to show it. But as far as I know, in the context where the secret-backup-operator runs, we do not have the name of the user who made the change. Try creating an issue for secret-backup-operator, and hope for the best 🙂

@arnaudbuchholz-sap
Copy link
Author

@hawser86 It looks like I need to submit an incident to the initial repository (the one you pointed out is a forked one).
Before doing so, I need to understand better how this backup is being done : you mentioned that the operator saves the backups regardless the tool, but is it triggered by the secret editor or is it triggered upon save (i.e. you don't have the opportunity to pass a parameter) ?

Thanks & regards

@hawser86
Copy link
Contributor

Honestly, it is some kind of kubernetes black magic I am not really familiar with. I think it is some kind of "hook" which is triggered automatically whenever a secret is modified, but it is not called by the Secret Editor directly, so we cannot pass an additional parameter.

@arnaudbuchholz-sap
Copy link
Author

@hawser86 that's what I wanted to understand. thx,

@arnaudbuchholz-sap
Copy link
Author

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