Zuplo Changelog

Previously, Zuplo maintained separate infrastructures for development environments (working copy) and production APIs. We have now migrated to a unified infrastructure, where development environments use the same environments as production APIs.

• Consistency: Development environments are now exactly the same as production and preview environments. This ensures that the behavior in development matches that in production, reducing the likelihood of unexpected issues after deployment.

• Global Reach: Development environments are now deployed to over 300 edge locations. This allows developers to test their changes in an environment that closely mimics the distributed nature of our production infrastructure.

• Scalability: Development environments are now fully scalable. This means that they can handle increased load when necessary, providing a more accurate representation of production performance.

• Deployment Time: The trade-off for these benefits is a slightly longer deployment time. However, we are actively working on optimizing our deployment processes to reduce this time.

We believe that the benefits of this change significantly outweigh the trade-offs, and we are excited to see how it improves our development process moving forward.

We are excited to announce the release of API Monetization, a new feature that enables developers to charge for use of their APIs. This feature is available to all Zuplo users and can be configured through the Zuplo Portal. This feature is currently in beta, and we welcome feedback from our users. We aim to make this feature generally available in the coming months.

For more detail see the blog post on API Monetization: API Monetization Release

Logging plugins now include several new fields to help filter logs for different environment types:

• environment: This is the name of your Zuplo environment. This will be the same as your Zuplo subdomain. i.e. if your Zuplo URL is https://silver-lemming-main-b0cef33.zuplo.app, the environment is silver-lemming-main-b0cef33
• environmentType: This indicates where your environment is running. Possible values are:
  • edge: Environments deployed to our 300+ edge locations
  • working-copy: Environments deployed to your single-instance dev server
  • local: When running with Zuplo local development
• environmentStage: This indicates the deployment stage of your environment. Possible values are:
  • production: Environments deployed from your default git branch
  • preview: Environments deployed from any other git branch
  • working-copy: Environments deployed to your single-instance dev server
  • local: When running with Zuplo local development

A new Log Plugin is available for SumoLogic that enables sending your API Gateway logs to SumoLogic.

See the documentation for information on how to setup the plugins. The following are all the log plugins currently available:

• DataDog
• Dynatrace
• Google Cloud Logging
• Loki
• SumoLogic

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.

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.