observe failed: cannot run refresh: refresh failed: unexpected end of JSON input

[linuxbsdfreak]

What happened?

observe failed: cannot run refresh: refresh failed: unexpected end of JSON input:

How can we reproduce it?

Create the following secret

 echo -n '{"username": "Dummy","password": "Dummy"}' | base64

apiVersion: v1
kind: Secret
metadata:
  name: fjjs5twp8v-secret
  namespace: upbound-system
data:
  data_json: eyJ1c2VybmFtZSI6ICJEdW1teSIsInBhc3N3b3JkIjogIkR1bW15In0=

k get secretv2s.kv.vault.upbound.io fjjs5twp8v-vault-secret -o yaml
apiVersion: kv.vault.upbound.io/v1alpha1
kind: SecretV2
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"kv.vault.upbound.io/v1alpha1","kind":"SecretV2","metadata":{"annotations":{},"labels":{"testing.upbound.io/example-name":"fjjs5twp8v-vault-secret"},"name":"fjjs5twp8v-vault-secret"},"spec":{"forProvider":{"dataJsonSecretRef":{"key":"data_json","name":"fjjs5twp8v-vault-secret","namespace":"upbound-system"},"mount":"eso-vault","name":"fjjs5twp8v-vault-secret"},"providerConfigRef":{"name":"vault-provider-config"}}}
  creationTimestamp: "2024-11-22T14:07:10Z"
  generation: 1
  labels:
    testing.upbound.io/example-name: fjjs5twp8v-vault-secret
  name: fjjs5twp8v-vault-secret
  resourceVersion: "7843182"
  uid: 0aad8c43-1ad9-4017-8197-e47eae5bc2e4
spec:
  deletionPolicy: Delete
  forProvider:
    dataJsonSecretRef:
      key: data_json
      name: fjjs5twp8v-vault-secret
      namespace: upbound-system
    mount: eso-vault
    name: fjjs5twp8v-vault-secret
  managementPolicies:
  - '*'
  providerConfigRef:
    name: vault-provider-config
status:
  atProvider: {}
  conditions:
  - lastTransitionTime: "2024-11-22T14:07:10Z"
    message: 'observe failed: cannot run refresh: refresh failed: unexpected end of
      JSON input: '
    reason: ReconcileError
    status: "False"
    type: Synced

What environment did it happen in?

Reconcilation does not work and provides the error

[FlochonR]

Hello !

I have the same error when I want delete my SecretV2. The secret is deleted but not the path ...

My policy authorizes the deletion with the capability "delete" in "toto/data/" and "toto/metadata/".

If I remove the finalizer manually, my ressource is well deleted.
I'm stuck without manual intervention.

I don't know if it's a misconfiguration in the provider or an issue with the finalizer :/