feat(messaging): add a messaging category with SQS and Pub/Sub

[TheSaifZaman]

Split out of #155 so each service lands on its own. Independent of #155 and #156 — this branch is off main.

The sidebar carried a route-less "Queue" placeholder that could never light up, while Floci core has had three seeded SQS queues the whole time:

$ curl -s .../aws/services/messaging/resources | jq -r '.[]|"\(.name) msgs=\(.metadata.approximateMessages)"'
orders-queue msgs=0
dead-letter-queue msgs=0
notifications-queue msgs=0

One category for both SQS and Pub/Sub rather than separate queue/topic ones: the delivery semantics differ, but a console renders both the same way — a named endpoint with a depth and a few settings — so splitting them would double the nav for nothing.

Contract details worth a look

• SQS ids. SQS addresses queues by URL, but a URL embeds the endpoint and changes if the runtime is re-pointed, which makes it a poor stable id. The adapter uses the queue name and resolves it via GetQueueUrl per call, as the AWS console does. Epoch-second timestamps are converted to the ISO strings the contract expects.
• FIFO. Attributes.FifoQueue=true is set for a .fifo name. Worth calling out because neither layer of verification caught its earlier absence: the unit stub accepted any input, and Floci core infers FIFO from the suffix so it worked locally too. It would only have failed against AWS. Caught in review on feat(gcp): add Cloud SQL and GKE adapters #155 and fixed here.
• Pub/Sub creates with PUT on the resource path, not POST to the collection.
• A queue whose GetQueueAttributes fails still lists, with detail omitted — a describe failure should degrade one row, not blank the table.

One SPI change

CloudResource.type was a closed union of eleven literals; queue, fifo-queue and topic are the first additions since. It is now open with a KnownResourceType alias documenting the convention — nothing dispatches exhaustively on it, so a closed union meant editing two packages per adapter for no safety. CloudServiceType stays closed, because that one is route-addressable and a typo there should 404.

The identical widening also appears on #156, so whichever lands second is a no-op for that hunk.

Adds @aws-sdk/client-sqs (both bun.lock and pnpm-lock.yaml updated — the API installs with bun --frozen-lockfile, which I learned the hard way).

Verification

pnpm lint, type-check, test, build pass. Live round-trip on both providers:

$ curl -X POST .../aws/services/messaging/resources -d '{"queueName":"probe","visibilityTimeout":"45"}'
  create: 201 → inspect: vis=45 arn=arn:aws:sqs:us-east-1:000000000000:probe → delete: 200 → 404

$ curl -X POST .../gcp/services/messaging/resources -d '{"topicName":"probe"}'
  create: 201 → list: [('probe','topic')] → delete: 200 → []

README service matrix regenerated from the registry.

Type of change

• Bug fix (fix:)
• New feature / service UI (feat:)
• Breaking change (feat!: or fix!:)
• Docs / chore

Area

• Frontend (packages/frontend)
• API / Cloud Proxy (packages/api)
• Cloud Explorer adapter / schema
• Build / CI / Docker

Checklist

• pnpm lint, pnpm type-check, pnpm test, and pnpm build pass locally
• New or updated tests added where it makes sense (bun test in packages/api)
• No fake/mock data added — unwired states stay empty or show an explicit placeholder
• Commit messages / PR title follow Conventional Commits

[greptile-apps]

Greptile Summary

Adds a schema-driven messaging category with AWS SQS and GCP Pub/Sub adapters registered on the cloud proxy.

• New AwsSqsAdapter (list/create/get/delete/health) using queue name as id, FIFO FifoQueue attribute, and SQS range validation
• New GcpPubSubAdapter creating topics via PUT on the resource path
• Opens CloudResource.type with KnownResourceType on API and frontend; wires client-sqs and registry entries; updates catalog display names and README matrix

Confidence Score: 5/5

The PR appears safe to merge; no blocking failures remain from prior threads or this follow-up pass.

No blocking failure remains.

Important Files Changed

Filename	Overview
packages/api/src/adapter-aws/AwsSqsAdapter.ts	SQS messaging adapter with name-based ids, attribute normalization, FIFO create, and range validation.
packages/api/src/adapter-gcp/GcpPubSubAdapter.ts	Pub/Sub topics adapter using PUT create and short topic ids.
packages/api/src/cloudProxy.ts	Registers AwsSqsAdapter and GcpPubSubAdapter on the shared registry.
packages/api/src/cloud-spi/types.ts	Widens CloudResource.type to KnownResourceType plus open string brand.
packages/api/src/cloud-spi/messagingSchema.ts	AWS/GCP messaging ServiceSchema fields, columns, and CRUD capabilities.

_{Reviews (4): Last reviewed commit: "chore(messaging): merge main into messag..." | Re-trigger Greptile}

[hectorvent]

Thanks Saif, this is a strong one. Using the queue name as the stable id and resolving it per call with GetQueueUrl matches what the AWS console does, and catching the FifoQueue attribute gap (which neither the stub nor Floci core would have surfaced) shows real care for the actual AWS contract. Both lockfiles are regenerated, tests are colocated and thorough on both adapters, and the catalog row follows the new AGENTS.md pattern exactly.

One coordination note before anything else: SQS and the messaging category are the most contested spot in the queue right now. Three earlier open PRs add SQS under a queue category (#137, #142, #148), and #144 and #146 also introduce a messaging category. I am coordinating the taxonomy (queue vs messaging) and how these land, so please treat that as an open question rather than settled by whichever PR merges first. Nothing for you to do yet, but a rebase or renaming may be requested once that call is made.

Two small things on the code itself, neither blocking:

1. The new doc comment on CloudResource.type gives sqs-queue as an example, but the adapter emits queue and fifo-queue. Could you align the example so the convention reads unambiguously?
2. visibilityTimeout and messageRetentionPeriod are free-text and passed straight through, so a non-numeric value only fails at the SQS call. A quick numeric check in create() with a ValidationError would give the form a friendlier error. Fine as a follow-up if you prefer.

The Pub/Sub PUT-on-resource-path detail and the degrade-one-row behavior on a failed describe are both exactly right. Nice work.

[TheSaifZaman]

Rebased onto fd3bd2f after #147, #152 and #155 merged. Mechanical: the CloudResource.type union collided with the 'secret' member #147 added, and cloudProxy.ts collided with the Cloud SQL and GKE registrations #155 added. Both resolved by keeping every member and every registration — never picking a side.

This branch's open KnownResourceType | (string & {}) union supersedes main's closed one, so the collision disappears for good once this lands.

README regenerated from service-matrix.ts rather than hand-merged, so it now shows both the Integration row this PR adds and the Key Vault column main gained.

Gate green after the rebase: lint, type-check, 463 tests, build.

[TheSaifZaman]

@hectorvent Both taken, thank you.

1. Doc example corrected. The CloudResource.type comment gave sqs-queue, which this adapter never emits — it is now fifo-queue, so the example is one of the values actually produced.

2. Numeric validation added, with SQS's own bounds rather than a generic "must be a number": visibilityTimeout 0–43200 and messageRetentionPeriod 60–1209600 seconds. Blank still means "omit the attribute", so the optional fields stay optional. Two tests: one for non-numeric and both out-of-range cases, one asserting a valid value is forwarded while a blank one is not.

Encoding the provider's range rather than just the type follows the same principle as the FifoQueue fix — the runtime would have accepted values real SQS rejects.

On the taxonomy coordination: understood, and no objection to whatever the maintainer decides. Flagging one input in case it is useful: this branch now carries the open KnownResourceType | (string & {}) union, so if messaging were renamed to queue or vice versa, the resource type values would not need to change — only the catalog slug and the schema. That should make the rename cheap whichever way it lands.

Gate green: lint, type-check, 465 tests, build. (I pushed a version with a type error in the test file first and amended it within the minute — the checks you see on the final SHA are the real ones.)

[hectorvent]

🎉 This PR is included in version 0.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀