Jeroen Op 't Eynde

Thanks for brining this up @pierluigilenoci _This was also discussed on the linked Slack thread but sharing here for posterity._ I've never seen this as a big issue as it...

The `connectionDetails` in my previous comment is the bit that does the mapping, also have a look here for a more comprehensive description to propagate connection details: https://github.com/crossplane/crossplane/discussions/2787

The provider secret value needs to look like this: ```json { "auth": "", "url": "" } ``` Assuming your secret object looks like this: ```yaml apiVersion: v1 kind: Secret metadata:...

Reopening as this should get documented somewhere properly.

@nkirpa The 'slug' or 'url' information is not returned upon creating a `ServiceAccountToken`, this makes it quite hard to return that information as part of the original secret. As a...

As you found out, that code is generated. When schemas upstream in grafana/grafana get updated with these fields, then this'll also appear in Grafonnet. See similar issue: https://github.com/grafana/grafonnet/issues/188 As suggested...

The docs are here: https://github.com/grafana/grafonnet/tree/main/docs however everything under `API/` is generated as well.

We're seeing this internally too, see https://github.com/grafana/terraform-provider-grafana/pull/1886 in an attempt to fix this.

I'm going to revert https://github.com/grafana/crossplane-provider-grafana/pull/135 as it causes a new bug instead of solving it.

I just ran into this as well, wildcard matching is essentially broken because of this.