What problem does it solve?
CloudBase function development can fail due to choosing the wrong function model, incorrect runtime packaging, missing scf_bootstrap for HTTP Functions, or misconfigured gateway/security access, causing broken endpoints, confusing logs, and slow iteration.
Core Features & Use Cases
- Event vs HTTP Function guidance: clearly separates the two runtime contracts (Event handler shape vs HTTP server on port 9000) so you implement the correct model from the start.
- Deployment-ready authoring rules: enforces Node.js HTTP Function packaging expectations (scf_bootstrap, port 9000, dependency bundling) and response/route handling discipline to avoid runtime contract mismatches.
- Operations and debugging pathways: directs you to the right tools for logs, gateway exposure, environment/config updates, and includes safe fallbacks when MCP is unavailable.
- Gotcha prevention: highlights common failure patterns like runtime immutability, wrong scf_bootstrap binary path, incorrect JSON/body handling, and confusing gateway access with runtime behavior.
Quick Start
Ask your agent to deploy an HTTP Function that listens on port 9000, includes the correct scf_bootstrap for Nodejs18.15, and configures public invocation rules if the endpoint must be accessible without authentication.