Zuplo Changelog

The new Request Body Validation policy allows validating incoming request bodies based on the schema in your OpenAPI file. This policy can be configured to reject requests with invalid body schemas or write logs to your preferred logging provider.

The Request Validation policy no supports validation of headers, query strings, and URL parameters.

Over the past few weeks we have shipped a number of improvements to the portal including:

• A new test running right in the Route designer
• A project info page in the settings tab
• Performance improvements when editing large OpenAPI files
• Subfolder support in the modules directory

The Mock API Response policy enables rapid mocking of an API using the examples inside of your OpenAPI document. Return a single example or random examples to build a proof-of-concept for your API or enable clients to begin development while the backend is being built out.

Proxy data or services from Firestore through Zuplo using two new policies.

• Upstream Firebase Admin Auth - authorizes requests using a Firebase Admin Token that can be used to call any Firebase API.
• Upstream Firebase User Auth - authorizes requests as a specific user which allows securing Firebase resources using security rules

The new Open API handler allows serving the public version of your OpenAPI file through a route of your choice.

The context.route property on the ZuploContext object now exposes the raw Open API operation JSON for use in handlers or policies.

export async function myHandler(request: ZuploRequest, context: ZuploContext) {
  const raw = context.route.raw();
  return raw;
}