Announcing the Ambassador Developer Portal with Swagger and OpenAPI support

Announcing the Ambassador Developer Portal with Swagger and OpenAPI support

  • October 5, 2019
Table of Contents

Announcing the Ambassador Developer Portal with Swagger and OpenAPI support

Today, we’re thrilled to announce the beta of Ambassador Developer Portal. The Developer Portal gives your developers a central self-service hub for your APIs. With the Developer Portal, developers are able to onboard and start using your APIs right away.

The Developer Portal beta includes the following features: To publish API documentation to the Developer Portal, update your service to pubish a Swagger or OpenAPI specification at .ambassador-internal/openapi-docs/. Then, publish your service to Kubernetes and register the service with an Ambassador Mapping. The Developer Portal will automatically detect the new service, and download the Swagger / OAPI specification from the internal URL. Both the content and look-and-feel of the Developer Portal are fully customizable.

The default content and templates are in the https://github.com/datawire/devportal-content repository. By pointing the Developer Portal to your own version of this repository, you can edit the content and layout as needed for your organization.

Source: getambassador.io

Tags :
Share :
comments powered by Disqus

Related Posts

Ambassador 0.50 GA Release Notes: SNI, New AuthService and Envoy v2 Support

Ambassador 0.50 GA Release Notes: SNI, New AuthService and Envoy v2 Support

Read More
Rate Limiting at the Edge

Rate Limiting at the Edge

I’m sure many of you have heard of the “Death Star Security” model—the hardening of the perimeter, without much attention paid to the inner core—and while this is generally considered bad form in the current cloud native landscape, there is still many things that do need to be implemented at edge in order to provide both operational and business logic support. One of these things is rate limiting. Modern applications and APIs can experience a burst of traffic over a short time period, for both good and bad reasons, but this needs to be managed well if your business model relies upon the successful completion of requests by paying customers.

Read More
Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

Ambassador and the Cloud Native Ecosystem—Part 1: Monitoring

In a Cloud Native world, microservices are running with ephemeral containers that are regularly deployed to multiple availability zones, regions, and even multiple clouds. As these cloud native applications become more complex, our supporting solutions like monitoring, have also had to become more complex. Today, more traditional monitoring responsibilities are being automated, and monitoring has become less human centric.

Read More