-
Notifications
You must be signed in to change notification settings - Fork 59
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 'fleet-server-insecure-http' setting from docs #1274
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
@nchaulet When you have a minute can you review this one, please? |
@kilfoyle I am not sure about that one, the UI do not allow to setup an |
Thanks @nchaulet! I'll update the parent issue accordingly. |
Actually, if the setting is used only for testing & development, perhaps we should just remove it from the docs anyway. What do you think? |
Yes it's probably better as there is no reason for an end user to use those settings |
(cherry picked from commit 735f788)
(cherry picked from commit 735f788) Co-authored-by: David Kilfoyle <[email protected]>
Apparently the setting
fleet-server-insecure-http
was removed by elastic/kibana#129371This updates the docs to remove mention of the removed setting.
Closes: #1273