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

Improve migration guide for security enabled by default #82677

Closed
bytebilly opened this issue Jan 17, 2022 · 4 comments · Fixed by #82816
Closed

Improve migration guide for security enabled by default #82677

bytebilly opened this issue Jan 17, 2022 · 4 comments · Fixed by #82816
Assignees
Labels
>docs General docs changes :Security/Security Security issues without another label Team:Docs Meta label for docs team Team:Security Meta label for security team v8.0.0

Comments

@bytebilly
Copy link
Contributor

Following up from #82128 (comment)_

The migration guide doesn't fully explain how to enable security features in 7.x before migrating to 8.0, and users may be tempted to just disable them explicitly.

We should improve the wording to point to our guides or something along those lines.

@bytebilly
Copy link
Contributor Author

@lockewritesdocs could you take a look when possible? Thanks!

@bytebilly bytebilly added :Security/Security Security issues without another label >docs General docs changes v8.0.0 labels Jan 17, 2022
@elasticmachine elasticmachine added Team:Security Meta label for security team Team:Docs Meta label for docs team labels Jan 17, 2022
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (Team:Security)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-docs (Team:Docs)

@lockewritesdocs
Copy link
Contributor

Closed via #82816

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
>docs General docs changes :Security/Security Security issues without another label Team:Docs Meta label for docs team Team:Security Meta label for security team v8.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants