-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
[v16] Update proxy features #47039
[v16] Update proxy features #47039
Conversation
Co-authored-by: Zac Bergquist <[email protected]>
Co-authored-by: rosstimothy <[email protected]>
Is there any way to move forward with the backports without breaking the ent builds/tests? |
I've opened the teleport.e backport and will only merge this one once the enterprise backport is approved, that should minimize the time the build is broken. The only change in this PR that breaks the tests/build is renaming |
It's always preferable if changes across oss and ent can be coordinated in a way that doesn't break the build, even if the break is only for a short period of time. |
@rosstimothy thanks, I've pushed a commit 111a174 that will prevent the teleport.e build from failing. Once the enterprise PR is backported, I'll create a new PR to revert it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @mcbattirola!
Backport #45979 to branch/v16
teleport.e PR: https://github.com/gravitational/teleport.e/pull/5104