feat: provision multiple SQS queue types per tenant#2
Draft
SethSharp wants to merge 1 commit into
Draft
Conversation
Tenant SyncQueueStep and SyncQueueAlarmStep now iterate over `aws.sqs.queues` in the manifest, creating one SQS queue and one CloudWatch depth alarm per configured type. Omitting the key defaults to `[default]`, preserving existing behaviour. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Tenant/SyncQueueStepiterates overaws.sqs.queuesin the manifest and provisions one SQS queue per configured type (e.g.default→yolo-{env}-{app}-{tenantId},high→yolo-{env}-{app}-{tenantId}-high)Tenant/SyncQueueAlarmStepfollows the same iteration, creating a CloudWatch depth alarm per queue type with a matching nameaws.sqs.queuesconfig, example, and naming conventionqueuesdefaults to[default]— fully backwards compatibleCloses LPX-647 (yolo-alpha scope). The LP-App side (SQS-HIGH connection,
HighPriorityQueuetrait,SwitchTenantwiring) is tracked separately.Test plan
yolo-alpha sync:multitenancy-tenants <env> --dry-runwithqueues: [default, high]— confirm two WOULD_CREATE results per tenant--dry-run— confirm both SQS queues and both CloudWatch alarms are created in AWSqueuesfrom manifest entirely — confirm existing single-queue behaviour is unchangedcoauthor: Jarvis 🤖