Feature Request: data source for aws_kinesis_stream #13521
Labels
Comments
cbroglie
pushed a commit
to cbroglie/terraform
that referenced
this issue
Apr 11, 2017
This fixes hashicorp#13521. This is the initial functioning implementation, but the docs still need to be updated, and a test needs to be written to validate the open and closed shards after an UpdateShardCount operation.
|
I still need to improve the tests and update the docs, but feedback on the initial implementation would be welcome, thanks |
|
Ok #13558 is ready to go |
cbroglie
pushed a commit
to cbroglie/terraform
that referenced
this issue
Apr 12, 2017
|
Actually I rebased the commits, #13562 is the new PR. |
stack72
pushed a commit
that referenced
this issue
Apr 20, 2017
|
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. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
ghost
locked and limited conversation to collaborators
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We process Kinesis Streams using ECS containers, and we need to scale the number of containers based on the number of shards in each stream. Since our ECS configuration is driven through Terraform, it would be great if we could access the shard count for a given stream via a data source.
I'm planning on submitting a PR for this, and will be exposing the following attributes which are returned by the DescribeStream and ListTagsForStream APIs:
arn(string)closed_shards(list of shard ids)creation_timestamp(int)name(string)open_shards(list of shard ids)retention_period(int)shard_level_metrics(list of metrics)status(string)tags(map)The only argument will be
name. Let me know if this sounds reasonable.The text was updated successfully, but these errors were encountered: