Closed haoliangyu closed 3 months ago
If I look at the payload in my browser's network tab, it looks like:
{
"httpMethod": "GET",
"oauthPassThru": false,
"sigV4AssumeRoleArn": "hello",
"sigV4Auth": true,
"sigV4AuthType": "ec2_iam_role",
"sigV4ExternalId": "13124",
"sigV4Region": "af-south-1"
}
So I think you've just got the wrong data. It looks OK in the UI when you go in the configure page because the workspace-iam-role
doesn't exist so it defaults to the ec2_iam_role
value which is saved when you click save
@julienduchesne Thanks for the debugging. The wrong value is one of the reason. Another reason is that I need to specify both sigV4AuthType
and sigv4AuthType
.
I hope the UI can provider the JSON configuration data (like the dashboard) and the error message can be clearer.
Terraform Version
1.9.1
Terraform Grafana Provider Version
3.0.0
Grafana Version
10.4
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
After running
terraform apply
, it should create the prometheus datasource in Grafana and the data source can read metrics. In Explorer, we can read the list of metrics.Actual Behavior
The prometheus data source is created and the configuration is the same as the one created manually with the
AWS Data Sources
app. However, when I open the Explorer, it shows a connection errorIf I go back to the data source configuration page and click the
Save & test
button without changing anything, it can read the metrics list again. It looks like the data source configuration is not properly saved or loaded during the terraform deployment.Steps to Reproduce
terraform apply
Save & test
button (with success)Important Factoids
This seems the regression of #516. It occurs when I try to add the data source of AWS Managed Prometheus to an AWS Managed Grafana workspace.
References
No response