You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am in the process of setting up the crossplane-terraform provider and can use its Workspace resource to create infrastructure, see its outputs in the status field, however when supplying publishConnectionDetailsTo it does not create a secret in any of the namespaces of the cluster.
The default StoreConfig exists and refers to kubernetes and the crossplane-system namespace.
How can we reproduce it?
Add this to your workspace:
publishConnectionDetailsTo:
name: xyz
See that it doesn't work for a tf module with outputs, however also see that the outputs are shown in the status field of your Workspace resource.
Please let me know, if I just made a mistake here or whether this should even work. If I'm not mistaken, then writeConnectionSecretToRef is supposed to be replaced by publishConnectionDetailsTo in the long run, so I did not want to add a soon-to-be-deprecated field to my infrastructure code.
The text was updated successfully, but these errors were encountered:
What happened?
I am in the process of setting up the crossplane-terraform provider and can use its Workspace resource to create infrastructure, see its outputs in the status field, however when supplying
publishConnectionDetailsTo
it does not create a secret in any of the namespaces of the cluster.The default StoreConfig exists and refers to kubernetes and the crossplane-system namespace.
How can we reproduce it?
Add this to your workspace:
See that it doesn't work for a tf module with outputs, however also see that the outputs are shown in the status field of your Workspace resource.
Now instead of adding the prior part, add this:
See that your secret gets created with the expected content.
What environment did it happen in?
Please let me know, if I just made a mistake here or whether this should even work. If I'm not mistaken, then
writeConnectionSecretToRef
is supposed to be replaced bypublishConnectionDetailsTo
in the long run, so I did not want to add a soon-to-be-deprecated field to my infrastructure code.The text was updated successfully, but these errors were encountered: