terraform-amg-config-module's Introduction

terraform-grafana-config-module

Terraform Documentation

Requirements

Name	Version
aws	>= 5.7.0
grafana	2.1.0

Providers

Name	Version
aws	>= 5.7.0
grafana	2.1.0

Modules

No modules.

Resources

Name	Type
aws_grafana_workspace_api_key.key	resource
aws_prometheus_rule_group_namespace.alarm_rule	resource
grafana_dashboard.dashboard_from_file	resource
grafana_data_source.data_source_from_map	resource
grafana_folder.dashboard_folders	resource

Inputs

Name	Description	Type	Default	Required
alarm_rules	The contents of the alarm rules file.	`string`	n/a	yes
aws_region	Contains the AWS Region that Grafana is running in.	`string`	`"us-east-1"`	no
dashboard_configs_folder	The path to the dashboards folder where the configuration files are located.	`string`	n/a	yes
data_source_map	A list of maps representing datasource information. Each map defines a data source with its type, name, and url.	`list(map(string))`	[ { "data_source_name": "CloudName1", "data_source_type": "cloudwatch", "data_source_url": "https://cloudwatch.amazonaws.com" }, { "data_source_name": "PromName1", "data_source_type": "prometheus", "data_source_url": "https://prometheus.amazonaws.com" }, { "data_source_name": "PromName2", "data_source_type": "prometheus", "data_source_url": "https://prometheus2.amazonaws.com" } ]	no
grafana_url	The url to your Grafana instance.	`string`	n/a	yes
grafana_workspace_id	The workspace ID of the grafana instance you wish to modify.	`string`	n/a	yes
prometheus_workspace_id	The workspace ID of the prometheus instance you wish to modify.	`string`	n/a	yes

Outputs

No outputs.

terraform-amg-config-module's People

Contributors

Watchers

terraform-amg-config-module's Issues

Data source values need to be more configurable to enable proper setup during application

The data source values need to have more exposed fields to enable proper configuration.

As it stands now, the data sources for X-Ray, Cloudwatch, and Prometheus won't work out of the box only being able to provide the endpoint.

Here's an example change to a working prom datasource manually configured and having automation re-apply defined values.

  # grafana_data_source.data_source_from_map["amp-us-east-1"] will be updated in-place
  ~ resource "grafana_data_source" "data_source_from_map" {
        id                 = "1:8"
      ~ json_data_encoded  = jsonencode(
          ~ {
              - prometheusType  = "Prometheus"
                # (8 unchanged attributes hidden)
            }
        )
        name               = "amp-us-east-1"
      ~ url                = "https://aps-workspaces.us-east-1.amazonaws.com/workspaces/<workspace id>/api/v1/query" -> "https://aps-workspaces.us-east-1.amazonaws.com/workspaces/<workspace id>/"
        # (6 unchanged attributes hidden)
    }

  # grafana_data_source.data_source_from_map["aws-cw-us-east-1"] will be updated in-place
  ~ resource "grafana_data_source" "data_source_from_map" {
        id                 = "1:9"
      ~ json_data_encoded  = jsonencode(
          ~ {
              - authType        = "ec2_iam_role"
              - defaultRegion   = "us-east-1"
              - logGroups       = [
                  - {
                      - accountId = "<account id>"
                      - arn       = "<arn>"
                      - name      = "<name>"
                    },
                ]
                # (8 unchanged attributes hidden)
            }
        )
        name               = "aws-cw-us-east-1"
        # (7 unchanged attributes hidden)
    }
  
    ````

Recommend Projects