[Bug]: aws_grafana_workspace_api_key doesn't renew
### Terraform Core Version 1.3.0 ### AWS Provider Version 4.32.0 ### Affected Resource(s) * aws_grafana_workspace_api_key * grafana provider ### Expected Behavior New key is created and terraform shows plan ### Actual Behavior ``` Error: Invalid provider configuration │ │ Provider "registry.terraform.io/grafana/grafana" requires explicit configuration. Add a provider block to the root module and configure the provider's required arguments as described in the provider │ documentation. │ ╵ ╷ │ Error: Missing required argument │ │ with provider["registry.terraform.io/grafana/grafana"], │ on <empty> line 0: │ (source code not available) │ │ "auth": one of `auth,cloud_api_key,oncall_access_token,sm_access_token` must be specified ``` Or if i have the grafana_data_source block also: ``` │ Error: the Grafana client is required for `grafana_data_source`. Set the auth and url provider attributes │ │ with grafana_data_source.prometheus, │ on main.tf line 50, in resource "grafana_data_source" "prometheus": │ 50: resource "grafana_data_source" "prometheus" { │ ``` ### Relevant Error/Panic Output Snippet _No response_ ### Terraform Configuration Files ``` provider "aws" { region = "us-west-1" } provider "grafana" { alias = "my_grafana" url = "https://${aws_grafana_workspace.my_aws_grafana.endpoint}" auth = aws_grafana_workspace_api_key.my_aws_grafana_key.key } resource "aws_grafana_workspace" "my_aws_grafana" { // timestamp needed to work aro
Posted by algojack on Oct 6, 2022, 10:48 AM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.2,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
[Bug]: aws_grafana_workspace_api_key doesn't renew
### Terraform Core Version 1.3.0 ### AWS Provider Version 4.32.0 ### Affected Resource(s) * aws_grafana_workspace_api_key * grafana provider ### Expected Behavior New key is created and terraform shows plan ### Actual Behavior ``` Error: Invalid provider configuration │ │ Provider "registry.terraform.io/grafana/grafana" requires explicit configuration. Add a provider block to the root module and configure the provider's required arguments as described in the provider │ documentation. │ ╵ ╷ │ Error: Missing required argument │ │ with provider["registry.terraform.io/grafana/grafana"], │ on <empty> line 0: │ (source code not available) │ │ "auth": one of `auth,cloud_api_key,oncall_access_token,sm_access_token` must be specified ``` Or if i have the grafana_data_source block also: ``` │ Error: the Grafana client is required for `grafana_data_source`. Set the auth and url provider attributes │ │ with grafana_data_source.prometheus, │ on main.tf line 50, in resource "grafana_data_source" "prometheus": │ 50: resource "grafana_data_source" "prometheus" { │ ``` ### Relevant Error/Panic Output Snippet _No response_ ### Terraform Configuration Files ``` provider "aws" { region = "us-west-1" } provider "grafana" { alias = "my_grafana" url = "https://${aws_grafana_workspace.my_aws_grafana.endpoint}" auth = aws_grafana_workspace_api_key.my_aws_grafana_key.key } resource "aws_grafana_workspace" "my_aws_grafana" { // timestamp needed to work aro
Comments (0)
No comments yet. Start the discussion.