[martypitt]

Adds an apiGateway { } component: LocalStack with API Gateway enabled, with OpenAPI documents imported as REST APIs and deployed to a stage. Orbital treats API Gateway as a schema registry (see vyne!2176), so this gives a stack something for it to browse and pull.

stack {
   apiGateway {
      restApi("pets", stage = "v1", openApi = petsOpenApi)
      restApiFromFile("orders", path = "/abs/orders.yaml")   // stage defaults to "prod"
   }
}

What's emitted

The component config is flat so Orbital exposes every value as an env variable:

Key	Env var (default component name)
accessKey, secretKey, region, endpointOverride	NEBULA_API_GATEWAY_ENDPOINT_OVERRIDE etc
<name>ApiId, <name>Stage, <name>InvokeUrl	NEBULA_API_GATEWAY_PETS_API_ID etc

Dashed API names are camel-cased (pet-store -> petStoreApiId). The docs page shows a connections.conf + registries.conf pair wired to these.

Notes

• REST APIs only: the community LocalStack image has no API Gateway v2 (HTTP APIs).
• The imported API answers requests only if the spec carries x-amazon-apigateway-integration blocks, as on AWS. Without them it exists for schema export, which is what Orbital's registry sync needs.
• restApiFromFile currently resolves on the Nebula server's filesystem, like s3 { file(path) }. Once feat(bundles): submit a stack together with the files it reads #70 (stack bundles) lands, it should resolve through resources.resolveFilePath(path) so files can ship with the stack.
• STS is enabled alongside API Gateway because Orbital's AWS connection health check calls GetCallerIdentity.

Tests

ApiGatewayExecutorTest runs against LocalStack: imports a spec, checks the OpenAPI export contains the path and schema, and checks the emitted config carries the API id, stage and invoke URL.

🤖 Generated with Claude Code

https://claude.ai/code/session_011c7t8dqC37eQzTt9o44x9v

[netlify]

✅ Deploy Preview for orbital-nebula canceled.

Name	Link
🔨 Latest commit	8ead2d1
🔍 Latest deploy log	https://app.netlify.com/projects/orbital-nebula/deploys/6ab271a5af90fb00084c0940

[martypitt]

Rebased onto main now that #70 (stack bundles) has merged. restApiFromFile(path) now resolves through resources.resolveFilePath(path), so a relative path reads a spec shipped with the stack, and an absolute path keeps reading the Nebula server's filesystem. Added a test covering the bundle case, and updated the docs examples to use a bundle-relative path.

🤖 — Claude

[martypitt]

Added stable API ids (070017c). importRestApi minted a fresh id on every stack start, which broke anything that had recorded one, such as an Orbital registry selection. The executor now creates the API with LocalStack's _custom_id_ tag, defaulting the id to the declared name in lower case, and imports the spec into it with putRestApi. restApi(..., apiId = "...") overrides it. Verified on LocalStack 3.0.2; tests cover the default and the explicit id.

Also documented that response schemas must be named models under components/schemas, since API Gateway drops inline schemas on import.

🤖 — Claude