Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.14 release: add support for traffic_policy #862

Merged
merged 7 commits into from
Aug 1, 2024

Conversation

TheConcierge
Copy link
Contributor

The agent has been updated to support sending policy as a string to the backend. This was added for both ephemeral tunnels and edge configurations with the API.

These changes are part of our ongoing effort to rename policy phases.

Copy link

vercel bot commented Jul 26, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
ngrok-docs ✅ Ready (Inspect) Visit Preview Aug 1, 2024 5:23pm

@TheConcierge
Copy link
Contributor Author

These are proposed docs changes for the agent release going out on Thursday

docs/agent/changelog.md Outdated Show resolved Hide resolved
Copy link
Contributor

@russorat russorat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. might need to also update the docs for the agent cli and config.

@TheConcierge TheConcierge merged commit f9d7482 into main Aug 1, 2024
3 checks passed
@TheConcierge TheConcierge deleted the ryan/agent-release-traffic-policy branch August 1, 2024 20:13
joelhans added a commit that referenced this pull request Aug 9, 2024
I noticed that after #862, some instances of example config files were
changed from `policy` to `traffic_policy`, but that hadn't reached the
Traffic Policy-specific doc ([example for
HTTP](https://ngrok.com/docs/http/traffic-policy/?cty=agent-config)) for
each type of endpoint.

This PR updates those three examples to update the naming. And fixes
what I believe to be malformed indentation in the TCP example.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants