feature request: parallelism parameter for resources with count
As a Terraform User, I should be able to specify a `parallelism` count on resource instances containing a `count` parameter So That I Can handle creating API resources via providers at a more sane rate and/or deal with mediocre api backends. ### Example Terraform Configuration File ```hcl resource "providera_resourcea" "many" { count = 1000 parallelism = 10 attributeA = "a" attributeB = "b" attributeC = "c" } ``` ### Expected Behavior **GIVEN** `terraform apply -parallelism = X` where `X` **<** `${providera_resourcea.many.*.parallelism)` **WHEN** terraform creates/deletes/refreshes resources **THEN** I expect only `X` concurrent goroutines creating this resource type. **GIVEN** `terraform apply -parallelism = X` where `X` **>=** `${providera_resourcea.many.*.parallelism)` **WHEN** terraform creates/deletes/refreshes resources **THEN** I expect only `${providera_resourcea.many.*.parallelism)` concurrent goroutines creating this resource type.
Posted by dkiser on May 5, 2017, 10:17 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
feature request: parallelism parameter for resources with count
As a Terraform User, I should be able to specify a `parallelism` count on resource instances containing a `count` parameter So That I Can handle creating API resources via providers at a more sane rate and/or deal with mediocre api backends. ### Example Terraform Configuration File ```hcl resource "providera_resourcea" "many" { count = 1000 parallelism = 10 attributeA = "a" attributeB = "b" attributeC = "c" } ``` ### Expected Behavior **GIVEN** `terraform apply -parallelism = X` where `X` **<** `${providera_resourcea.many.*.parallelism)` **WHEN** terraform creates/deletes/refreshes resources **THEN** I expect only `X` concurrent goroutines creating this resource type. **GIVEN** `terraform apply -parallelism = X` where `X` **>=** `${providera_resourcea.many.*.parallelism)` **WHEN** terraform creates/deletes/refreshes resources **THEN** I expect only `${providera_resourcea.many.*.parallelism)` concurrent goroutines creating this resource type.
Comments (0)
No comments yet. Start the discussion.