Skip to content

CHANGELOG.md

Latest commit

 

History

History
53 lines (37 loc) · 2.7 KB

CHANGELOG.md

File metadata and controls

53 lines (37 loc) · 2.7 KB

0.12.0

  • BREAKING: Upgraded reqwest from 0.11 to 0.12. If you pass a custom reqwest::Client via the builder, you must upgrade your reqwest dependency to 0.12.
  • Switched TLS backend from native-tls to rustls-tls to fix compilation failures with recent Rust nightly toolchains.

0.11.0

  • Add support for resolves_to on Reserved Domains.
  • Deprecate API filtering via id and url query parameters. Please migrate to the filtering syntax described in API Filtering.

0.10.0

  • Add support for CEL filtering when listing resources.
  • Add support for service users
  • Add support for vault_name on Secrets
  • Make pooling_enabled on Endpoints optional

0.9.0

  • Change endpoint filtering query parameters to id and url.
  • Add support for getting secrets by vault.

0.8.0

  • Add support for ids and urls query parameters when listing endpoint resources.

0.7.0

  • Renamed upstream_proto to upstream_protocol for endpoint resources
  • Added support for pooling_enabled on Endpoints
  • Add support for vaults
  • Add support for secrets

0.6.0

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

0.5.0

  • Added principal for endpoint resources

0.4.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.

0.3.0

  • 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.

  • Added support for the 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.

0.2.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.

0.1.0

  • Initial release