Upgrade to 2.x fails due to 'No vaults found with identifier "<vault_name>"

[brujoand]

Your environment

Chart Version: 2.0.2

Helm Version: v3.17.2

Kubernetes Version: v1.32.4

What happened?

I upgraded the chart, from 1.17.x while following the discussion from #232. I deploying the upgrade along with the additional value: operator.authMethod: "connect". The connect pod and operator pod both came up and are in a running state. The connect-sync and connect-api containers both log only happy things. But the onepassword-connect container is angry and yelling over and over:

2025-07-24T09:24:15Z	ERROR	Reconciler error	{"controller": "onepassworditem", "controllerGroup": "onepassword.com", "controllerKind": "OnePasswordItem", "OnePasswordItem": {"name":"frigate-cameras","namespace":"automation"}, "namespace": "automation", "name": "frigate-cameras", "reconcileID": "db40e8e2-1558-4157-8cbd-f69bd2b2228c", "error": "failed to retrieve item: failed to 'getVaultID' for vaultNameOrID='homelab': No vaults found with identifier \"homelab\""}

What did you expect to happen?

I expected everything to keep working

Steps to reproduce

1. Have a working 1.17.x deployment
2. Upgrade while setting the authMethod to "connect"
3. Fail

Notes & Logs

[brujoand]

Soo. It turns out that the vault name now needs to be in the correct casing, previously it did not. Meaning I had to change:

  itemPath: "vaults/homelab/items/Frigate"

into

  itemPath: "vaults/Homelab/items/Frigate"

[scottmuc-mo]

Thanks @brujoand for reporting this! I just observed the same behaviour. This is a serious one and I can see it catching a lot of people off guard.

[volodymyrZotov]

Thank you for reporting @brujoand . We'll take a look into this! 👨‍💻

[scottmuc-mo]

@volodymyrZotov fyi, I tested to see if the actual items are case-sensitive after the upgrade, and it appears that they aren't. It's just the vault name.

[volodymyrZotov]

Thanks for figuring this out @scottmuc-mo !