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

Docs: Remove -ignore deprecated #879

Conversation

eleijonmarck
Copy link
Contributor

No description provided.

@github-actions
Copy link

In order to lower resource usage and have a faster runtime, PRs will not run Cloud tests automatically. To do so, a Grafana Labs employee must promote the Drone build.

For maintainers, it's better to run only the Cloud tests you need, rather than all of them. You can do so by setting the following parameter when promoting:

TESTARGS='-run=<testname>'

@@ -1,7 +1,7 @@
#!/usr/bin/env bash

# Generate docs!
go run github.com/hashicorp/terraform-plugin-docs/cmd/tfplugindocs -ignore-deprecated
go run github.com/hashicorp/terraform-plugin-docs/cmd/tfplugindocs
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is the meat of the change

@@ -18,6 +18,8 @@ func ResourceAPIKey() *schema.Resource {
return &schema.Resource{
Description: `Manages a single API key on the Grafana Cloud portal (on the organization level)
* [API documentation](https://grafana.com/docs/grafana-cloud/reference/cloud-api/#api-keys)

!> Deprecated: please use ` + "`grafana_cloud_stack_service_account`" + ` and ` + "`grafana_cloud_stack_service_account_token`" + ` instead, see [Migrate API keys to Grafana service accounts using Terraform](https://grafana.com/docs/grafana-cloud/reference/migrate-api-keys-to-service-accounts/) for more information.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the wrong resource. This is a Cloud API key, this is absolutely not deprecated. What we should have deprecated is the cloud_stack_api_key resource

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think we have to revisit the previous PR then - https://github.com/grafana/terraform-provider-grafana/pull/872/files#diff-04961555cdd45e8547f47c42af9a867501a2b2ebf4004768ae8d8830d728f77eR28

as we deprecated the cloud_api_key and not the cloud_stack one

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

il update this PR with these changes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

see 4db6be8

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

does this mean we have to make a new release no?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I will

Copy link
Member

@julienduchesne julienduchesne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@eleijonmarck eleijonmarck marked this pull request as ready for review April 13, 2023 14:39
@eleijonmarck eleijonmarck requested a review from a team as a code owner April 13, 2023 14:39
@julienduchesne julienduchesne merged commit 139a2d8 into master Apr 13, 2023
@julienduchesne julienduchesne deleted the eleijonmarck/docs/remote-ignore-depreacted-for-docs-to-show branch April 13, 2023 14:45
@sg-qwt
Copy link

sg-qwt commented Sep 18, 2023

@julienduchesne From the docs linked https://grafana.com/docs/grafana-cloud/developer-resources/api-reference/cloud-api/#api-keys it says: Caution: Cloud API keys are now deprecated. Use [Cloud Access Policies](https://grafana.com/docs/grafana-cloud/developer-resources/api-reference/cloud-api/#access-policies-and-tokens) instead. Does this mean this resource is also deprecated in favor of grafana_cloud_access_policy and grafana_cloud_access_policy_token?

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

Successfully merging this pull request may close these issues.

3 participants