Ben Ash
Ben Ash
Hi @toasahi, currently, VSO does not support the use-case described in this issue, rather it relies on the interval set from the last sync. We plan to extend VSO to...
@nia-potato VSO will only log at the error level when it encounters an error. Are you experiencing something else? Thanks, Ben
@chrysalis69 - thanks for pointing this out. We are going to take a closer look to see how best to support this enhancement.
Released in https://github.com/hashicorp/vault-secrets-operator/releases/tag/v0.7.0
Hi @alexdga, I think the solution you are looking for is here: https://github.com/hashicorp/vault-secrets-operator/issues/619#issuecomment-1984053146 - Please let us know if you require any further assistance.
Closing this issue out, as the solution is mentioned here: https://github.com/hashicorp/vault-secrets-operator/issues/619#issuecomment-1984053146
Hi @sebglon , would you be able to provide any VSO error logs/events that you encountered? The last event seems to be normal after having restarted VSO. Thanks, Ben
Hi @sizgiyaev , just wanted to let you know that we are currently working this issue. It should go out in the next VSO release. No ETA yet for that,...
So we took a closer look at this issue. Essentially, VSO does not yet support notification on updates to a Vault Secret engine's backend configuration. It can only rely on...
Of note I was unable to reproduce the issue where the AWS secret's engine did not properly create the AWS IAM user after receiving a request from VSO.