-
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
Remove Assist #42657
Remove Assist #42657
Conversation
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.
Bot
Can we get rid of |
@zmb3 I removed it as well (and all related code) |
511d1de
to
02ede86
Compare
e
Outdated
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.
This looks like a mistake.
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. Fixed
02ede86
to
3f87482
Compare
// Assist is a set of options related to the Teleport Assist feature. | ||
Assist *AuthAssistOptions `yaml:"assist,omitempty"` | ||
|
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.
@jakule this will break teleport
startup after upgrade if the field is set with a message like
ERROR: failed parsing the config file: yaml: unmarshal errors: line 41: field assist not found in type config.Auth
Which I just hit trying to patch my staging tenant.
And we still document that field in both auth and proxy service config reference:
https://goteleport.com/docs/reference/config
changelog: Teleport Assist has been removed