-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
New Resource - QLDB Data Streams #17471
Comments
Good point, I updated that 😅 |
Seems like there isn't much interest in this, so I will make an attempt at this myself 😅 |
After doing some digging, it looks like the potential terraform configuration should look more like this: resource "aws_qldb_stream" "sample-ledger-stream" {
ledger_name = "existing-ledger-name"
stream_name = "sample-ledger-stream"
role_arn = "arn:aws:iam::xxxxxxxxxxxx:role/service-role/sample-role-arn"
inclusive_start_time = "2021-01-01T00:00:00Z"
kinesis_configuration = {
aggegation_enabled = false
stream_arn = "arn:aws:kinesis:us-east-1:xxxxxxxxxxxx:stream/example-kinesis-stream"
}
tags = {
"example" = "tag"
}
} Lmk if anyone has thoughts on this 🤔 |
This functionality has been released in v4.10.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Description
From the docs:
A key thing to note here is that a QLDB instance can have many data streams.
New or Affected Resource(s)
aws_qldb_stream
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: