creation of custom system doesn't populate connection secret about provider-styra HOT 7 CLOSED

@janwillies PoC:

$ kubectl -n crossplane-system get secrets connection-details -o yaml        
apiVersion: v1
data:
  opaConfig: ZGlzY292ZXJ ... xL2J1bmRsZXMK
kind: Secret
metadata:
  creationTimestamp: "2022-01-21T15:21:05Z"
  name: connection-details
  namespace: crossplane-system
  ownerReferences:
  - apiVersion: styra.crossplane.io/v1alpha1
    controller: true
    kind: System
    name: example-system
    uid: 93a3842a-ca47-4414-a17e-6b1831761433
  resourceVersion: "1202051"
  uid: eedf4b10-5251-4762-820f-505c47c94c7a
type: connection.crossplane.io/v1alpha1

from provider-styra.

Sorry, I misunderstood your issue with something that sounded similar.

Yes, you are right, we currently only support Styra's kubernetes and kubernetes:v2 for connection secrets. Instead of the helm values we could fetch the OPA config from /v1/systems/<system-id>/assets/opa-config and write it out as connection secret.

from provider-styra.

This issue should be fixed by now. Are you running the latest version?

from provider-styra.

I was running 7f325a5 when I tested.

I'm referring to this part of the code: https://github.com/crossplane-contrib/provider-styra/blob/main/pkg/controller/system/controller.go#L357-L363

Note that I'm trying to create a system of type custom here.

from provider-styra.

You have to create a system of type kubernetes or better kubernetes:v2. Only for those does Styra provide a helm chart.

from provider-styra.

But I want to create a system of type custom :)

I opened the issue to see if that's something provider-styra is able to support.

from provider-styra.

Fixed in #23

from provider-styra.