Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose oncall_access_token from within the Grafana Terraform provider's grafana_cloud_stack resource #4591

Open
Alex3k opened this issue Jun 26, 2024 · 7 comments

Comments

@Alex3k
Copy link

Alex3k commented Jun 26, 2024

What would you like to see!

Today to fully automate OnCall you use Oncall resources within a Grafana provider and pass the oncall_access_token which seems to only be accessible via the UI.

This poses a major challenge when trying to automate everything end to end because I don't want to go into the UI after creating a grafana cloud stack via terraform, then trigger more automation to automate terraform.

It would be much easier if this token was accessible within the grafana_cloud_stack resource so that I can automate everything end to end without any human intervention

Product Area

Terraform/Crossplane

Anything else to add?

No response

Copy link
Contributor

The current version of Grafana OnCall, at the time this issue was opened, is v1.7.2. If your issue pertains to an older version of Grafana OnCall, please be sure to list it in the PR description. Thank you 😄!

@iskhakov
Copy link
Contributor

iskhakov commented Jun 26, 2024

It is probably easier to support Grafana Service Accounts, and get rid of OnCall API keys completely
See #3812 (comment)

@vstpme
Copy link
Member

vstpme commented Sep 25, 2024

@joeyorlando @matiasb should we close this one / reschedule?

@FecoDoo
Copy link

FecoDoo commented Dec 8, 2024

This is a very needed feature as it's blocking any automation possibilities with Terraform, regardless of where to obtain the token from (SA or oncall plugin). Is there any update on this?

@matiasb
Copy link
Contributor

matiasb commented Jan 7, 2025

This is a very needed feature as it's blocking any automation possibilities with Terraform, regardless of where to obtain the token from (SA or oncall plugin). Is there any update on this?

FYI, it is now possible to manage OnCall resources authenticating the provider via a service account token.

@FecoDoo
Copy link

FecoDoo commented Jan 8, 2025

This is a very needed feature as it's blocking any automation possibilities with Terraform, regardless of where to obtain the token from (SA or oncall plugin). Is there any update on this?

FYI, it is now possible to manage OnCall resources authenticating the provider via a service account token.

Thanks, but AFAIK the service account for oncall is auto created with externalServiceAccounts feature toggle, and there's no way (at least I couldn't find) to obtain the pre-populated token with Grafana Terraform provider.

@matiasb
Copy link
Contributor

matiasb commented Jan 13, 2025

This is a very needed feature as it's blocking any automation possibilities with Terraform, regardless of where to obtain the token from (SA or oncall plugin). Is there any update on this?

FYI, it is now possible to manage OnCall resources authenticating the provider via a service account token.

Thanks, but AFAIK the service account for oncall is auto created with externalServiceAccounts feature toggle, and there's no way (at least I couldn't find) to obtain the pre-populated token with Grafana Terraform provider.

You should create a service account (and token) as described in the docs, ie. via a cloud access token, and use that to manage OnCall resources too. You should also be able to setup a service account in OSS setups. So, you won't be using the plugin external service account but your own. Makes sense?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants