What happened?
When a managed resource uses a sensitive secret reference inside a list item (e.g. spec.forProvider.options[0].configurationSecretRef), Upjet may attempt to inject secret data into Terraform state using a TF path that contains a wildcard (e.g. options[*].configuration.<key>).
This fails with an error similar to:
cannot set string as terraform attribute for fieldpath "options[*].configuration.<key>": options is not an object
How can we reproduce it?
-
Run an Upjet-based provider (e.g. provider-auth0).
-
Create a Connection that sets spec.forProvider.options[0].configurationSecretRef (or any secret ref under options).
-
Reconcile the resource.
-
Observe reconcile failing when Upjet tries to inject secret data into Terraform using a wildcard TF path like options[*].configuration., resulting in the error mentioned.
What happened?
When a managed resource uses a sensitive secret reference inside a list item (e.g.
spec.forProvider.options[0].configurationSecretRef), Upjet may attempt to inject secret data into Terraform state using a TF path that contains a wildcard (e.g.options[*].configuration.<key>).This fails with an error similar to:
cannot set string as terraform attribute for fieldpath "options[*].configuration.<key>": options is not an objectHow can we reproduce it?
Run an Upjet-based provider (e.g. provider-auth0).
Create a Connection that sets spec.forProvider.options[0].configurationSecretRef (or any secret ref under options).
Reconcile the resource.
Observe reconcile failing when Upjet tries to inject secret data into Terraform using a wildcard TF path like options[*].configuration., resulting in the error mentioned.