Skip to content

Add dynamic_throttled_queues#237

Open
Jkovarik wants to merge 5 commits intomainfrom
jk/ETQ-196-add-dynamic-queues
Open

Add dynamic_throttled_queues#237
Jkovarik wants to merge 5 commits intomainfrom
jk/ETQ-196-add-dynamic-queues

Conversation

@Jkovarik
Copy link
Copy Markdown
Collaborator

This PR adds a way to dynamically configure throttled queues in cases where the same queue is being deployed across multiple deployments and/or accounts rather than redefining the queue per deployment.

@Jkovarik Jkovarik marked this pull request as ready for review March 12, 2026 16:18
}
output "send_pan_task" {
value = module.cumulus.send_pan_task
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Related?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sort-of. This work was tested/based off of #235, I just missed it hadn't been merged yet.

I'll clean this up, it's not needed for the main merge.


## Unreleased

* Add dynamic_throttled_queues to allow for throttled queues with configurable names to be defined according to the pattern: https://sqs.${data.aws_region.current.name}.amazonaws.com/${data.aws_caller_identity.current.account_id}/${local.prefix}-${q.queue_name}. This allows for queue configurations to be defined programatically for similar deployments across deployment/account/regions/etc.
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dumb question: Are "Throttled Queues" a well-defined thing? I know what you mean. You know what you mean. Do we need to define what we mean?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a fair point - I think in the context of the ecosystem and Cirrus.... probably. We could include a link to the Core docs though, if you think that's helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants