Simon Barendse

Also [requested here](https://1password.community/discussion/comment/607546/#Comment_607546).

Hi @hgarrow, were you able to reproduce the issue? I'm interested to learn if there's more we should do. If you are still running in to this error - do...

Thank you for opening this issue. We're investigating options to allow dynamically watching namespaces without requiring an update or restart. Note that you can already set `WATCH_NAMESPACE` to the empty...

Definitely Mark! Thank you for pointing this out. I've opened https://github.com/1Password/onepassword-operator/pull/39 to address this.

I'm curious to learn if this was just a documentation issue or there's more we can do. @csullivannet @pdavisfmnh @camilb and @liftedkilt, will watching all namespaces work for your use...

Hello Klaus, Let me make sure I'm understanding your use case fully: Are you trying to apply least privilege among your dev teams by using a different operator/credential per dev...

Thank you, Klaus, for the additional context! I think your assessment is correct and we do not currently have something in place to narrow down access for an all-namespace operator....

We've done the same thing as you suggest in https://github.com/secrethub/secrethub-circleci-orb/pull/39. Shall I submit a PR that adds the `keep-dev-orb` from that PR?

Could we change those list operations to list the deployments and secrets in the watched namespaces specifically? We could then [add a list permission for deployments](https://github.com/1Password/connect-helm-charts/blob/55746b857861a85cf0e8f7c962c2cc55804f155a/charts/connect/templates/clusterrole.yaml#L72) so the operator is...

https://github.com/secrethub/secrethub-cli/pull/285 contains a MVP of shipping a Terraform state backend with the SecretHub CLI.