Please add a Github description so other tools like https://github.com/luebken/awesome-crossplane-providers can pull what this provider is about.

What happened?

GetConfig does not use the SecretRef.Key field in ProviderConfig and always looks up the field token.

How can we reproduce it?

Create a ProviderConfig that references a different field than token and a secret that does not have an entry for token.

Create a System resource that references this config and the reconcile will fail.

What environment did it happen in?

Running build 7301535

What problem are you facing?

Some Styra features like datasources require credentials which are uploaded and stored as secrets.

How could Crossplane help solve your problem?

provider-styra should provide a new Secret resource that matches the Styra secret API.

What problem are you facing?

Styra released a new OpenAPI spec for their API and deprecated the old one. While the endpoints have not changed, it should be considered to update the client and use the renamed struct names to be on the safe side:

https://docs.styra.com/reference/api/openapi/

How could Crossplane help solve your problem?

Update the client with the new swagger spec so provider-styra does not rely on an old API definition.

What problem are you facing?

I want to manage access to systems in a more fine granular way, so that I can grant access only to a single system

How could Crossplane help solve your problem?

implement the rolebinding resource

What problem are you facing?

I wanted to create a System and looked for the available types but couldn't find any

It looks like there is at least:

• custom
• envoy
• kubernetes
• kubernetes:v2
• terraform(?)

I wasn't able to figure it out from the styra docs either.

How could provider-styra help solve your problem?

Maybe we can list them here: https://github.com/crossplane-contrib/provider-styra/blob/main/apis/system/v1alpha1/system.go#L55

What problem are you facing?

We are using Styra datasources and want to manage them via Crossplane/provider-styra.

How could Crossplane help solve your problem?

provider-styra should provide a new resource DataSource that matches the Styra datasource API

What happened?

I tried to create a system with type custom. The system was created correctly at the styra das api, but the connection secret in kubernetes was empty.

I expected to find the api token in there, or the opa conf, so I can register my opa deployment with the styra das system

How can we reproduce it?

create a custom system like this:

apiVersion: styra.crossplane.io/v1alpha1
kind: System
metadata:
  name: custom-system-demo
spec:
  forProvider:
    description: testing custom opa system
    type: custom
  providerConfigRef:
    name: styra-provider
  writeConnectionSecretToRef:
    name: custom-system-demo
    namespace: crossplane-system

What environment did it happen in?

provider-styra version: 7f325a5

What problem are you facing?

The readme is currently lacking setup instructions.

How could Crossplane help solve your problem?

Extend readme.md with steps that explain how to setup provider-styra, connect it to a Styra instance and deploy resources.