Open sentros opened 3 months ago
Voting for Prioritization
Volunteering to Work on This Issue
At the API level Timestream for InfluxDB is a distinct service. Following our naming guidelines the first resource should be:
resource "aws_timestreaminfluxdb_db_instance" "example" {
name = "..."
}
I would like to work on this issue.
I am working on the aws_timestreaminfluxdb_db_instance
resource and will provide updates in the coming weeks.
So far, my implementation differs in a few ways from the proposed implementation.
aws_timestreaminfluxdb_provider_group
resource.
aws_timestreaminfluxdb_db_instance
resource; users will have to create this provider group themselves, without Terraform.S3 log buckets will follow the format defined by AWS SDK Go V2. Instead of providing an S3 bucket ID for logging, users will provide the following:
log_delivery_configuration {
s3_configuration {
bucket_name = aws_s3_bucket.example.bucket
enabled = true
}
}
Description
It's now possible to select a different engine for a Timestream database in the aws console. The previous engine is now called LiveAnalytics and a new engine was added called InfluxDB. Terraform has no support for the InfluxDB engine or for its configuration options.
If you plan to add the new engine as an option to the pre existing aws_timestreamwrite_database you could just add new parameters for it as shown in the example. At least the parameter group needs its own new resource.
Not much is shared between the engines so maybe a whole new resource for InfluxDB type Timestream would be better. For example the RDS resource handles engine types all in the same resource but RDS engine types at least share some configuration options between them as opposed to Timestream for LiveAnalytics vs InfluxDB.
Affected Resource(s) and/or Data Source(s)
aws_timestreamwrite_database
Potential Terraform Configuration
References
Would you like to implement a fix?
None