API tokens and implications of `/install` endpoint about synthetic-monitoring-api-go-client HOT 4 CLOSED

Thanks again for the quick response, this was indeed all I needed to know to implement my use case. I will close the issue from my side.

from synthetic-monitoring-api-go-client.

Hi @kiview,

I wonder if using this library and the documented REST API is the right approach for automating the creation of checks as a Grafana Cloud user.

You can use this library or Grafana Terraform provider to manage checks and private probes. we recommend using Terraform provider if Terraform is already part of your tooling.

/install call is used to get a synthetic monitoring api-token, and that token need to be passed for all the calls that require Authentication.

/install should be called only once, and token can be saved somewhere safe, and reused for all the subsequent calls to other endpoints that require Authentication

Also, what is the reason to not use the Grafana API token directly for the authentication of the other endpoints?

we are working on making automation experience better.

I am getting Terraform provider added in docs so it's easy to discover :)

from synthetic-monitoring-api-go-client.

Thank you very much for the detailed answer @electron0zero.

I am unsure if we want to incorporate the Terraform provider atm, but the clarification of the token obtained by using the /install endpoint was very helpful. Am I correct that the token provided by /install has an unlimited lifetime?

from synthetic-monitoring-api-go-client.

Am I correct that the token provided by /install has an unlimited lifetime?

Yes, token obtained from /install do not expire.

from synthetic-monitoring-api-go-client.