[DOC] Mention base_path change in 2.8.0 release notes#6844
[DOC] Mention base_path change in 2.8.0 release notes#6844barkbay merged 6 commits intoelastic:mainfrom
Conversation
pebrc
left a comment
pebrc
left a comment
There was a problem hiding this comment.
LGTM. Is this a "breaking" change?
Only if user attempted to set it in the past, and forgot it is set while it's actually not used by the current version of ECK. In such a case, upgrading to |
I'd say it's not a breaking change because we don't break anything if you don't make a mistake but if you do, it will break you. I'd therefore be on the side of caution and I'll present this change as a breaking change. |
|
Thanks @thbkrkr, I'll add a breaking change in the changelog. |
|
@thbkrkr I also took advantage of this PR to regenerate |
|
@elasticmachine run elasticsearch-ci/docs |
thbkrkr
left a comment
thbkrkr
left a comment
There was a problem hiding this comment.
Nit: Sorry if I'm a bit late but I think we should rename "Copy Elasticsearch configuration files before creating links" #6703 in something like "Hardened Security Context for Elasticsarch".
I think there are people who only read the release notes and not the highlights.
|
buildkite test this |
|
I think docs failure is related to elastic/apm-server#10891? |
|
@elasticmachine run elasticsearch-ci/docs |
* [DOC] Mention base_path change in 2.8.0 release notes * Tag 6689 as a breaking change * Regenerate docs/release-notes/2.8.0.asciidoc
3 participants
Fixes #6702