Feature Request: Force Synchronization of Secrets Managed by Other Resources

[marcosmamorim]

I'm proposing a new feature for the bitwarden-k8s-secrets-manager that would add the capability to force synchronize secrets even if they are currently managed by other resources. This feature would be particularly useful for migration scenarios where secrets initially set up by other applications (like Helm for Kubernetes deployments) need to be taken over and managed by bitwarden-k8s-secrets-manager.

Use Case Example:

Consider a scenario where an application is deployed using Helm, which automatically creates several secrets. Over time, it may become necessary to migrate the management of these secrets to bitwarden-k8s-secrets-manager. Currently, if a secret is already managed by Helm, there's no straightforward way to have bitwarden-k8s-secrets-manager take over without manual intervention.

[9strands]

Hi, @marcosmamorim!

After discussion with @jkupferer - we're not sure this should be automated due to potential conflict between tools. Mostly, for something like helm, the process would be to remove the helm-labels so that helm will no longer attempt to touch it. So, it could be done, but we would just tell helm to ignore the resource in an update, and then either delete the secret (so bitwarden can recreate) or update the labels so bitwarden-k8s-secrets-manager would take over.

Do you have other thoughts on this?