v7.2.0

v7.2.0

• Add support for pooling_enabled on Endpoints.

Full Changelog: v7.1.0...v7.2.0

v7.1.0

v7.1.0

• Added support for KubernetesOperators and Bindings (currently in private beta).

Breaking Changes

• Renamed upstream_proto to upstream_protocol for endpoint resources

v6.1.0

v6.1.0

• Added support for Cloud Endpoints (currently in private beta).

v6.0.0

Renamed the Policy Module to the Traffic Policy Module on HTTP Edge Routes, TCP Edges, and TLS Edges, which allows you to configure rules that can be used to influence and control traffic to and from your upstream service. The Traffic Policy itself is now specified as either a JSON or YAML string.

v5.4.1

What's Changed

Fixes

• Update generated files by @ngrok-ci in #44 - Fixed an issue with pagination for some resources, like reserved_addrs, by using the next_page_uri returned in the response instead of the id of the last resource.

Full Changelog: v5.4.0...v5.4.1

v5.4.0

ENHANCEMENTS:

Added support for the Bot User API. The Bot User API allows you to manage the bots that are registered to your ngrok account. You can automate the creation, management, and deletion of bot users in your account.

v5.3.1

INTERNAL:

• Moved location of BaseClient

v5.3.0

ENHANCEMENTS:

• Added support for the Traffic Policy module on TCP edges, TLS edges, and HTTPS edge routes. A Traffic Policy allows traffic to and from your edges to be shaped and influenced by defining rules that contain expression to filter the traffic and actions to take effect.
• Added static_backend resource, which defines a static address at which traffic should be forwarded.

v5.2.0

• Added JWT Validation edge route module client and datatype
• Added User Agent Filter edge route module client and datatype

v5.1.0

ENHANCEMENTS:

• Added owner_id field to the api_key, credential, and ssh_credential resources. If supplied at credential creation, ownership will be assigned to the specified User or Bot. Only admins may specify an owner other than themselves. Defaults to the authenticated User or Bot.
• Added failover_backend, http_response_backend, and tunnel_group_backend resources. A Failover backend defines failover behavior within a list of referenced backends. Traffic is sent to the first backend in the list. If that backend is offline or no connection can be established, ngrok attempts to connect to the next backend in the list until one is successful.