ECS current to 8.11 - #2893
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. |
kilfoyle
left a comment
There was a problem hiding this comment.
LGTM!
As long as this passes CI checks it should be good to go. 🚀
|
I'm not convinced this will pass link-checking, but we'll see. After this is merged, we'll need to merge master into @abdonpijpelink's 8.12 PR: #2862 |
|
@bmorelli25 Looks like you called it not passing CI. Does that mean it's not possible to omit an ECS version? |
|
It doesn't mean it's not possible. It just means it's going to be a much more complex process than this PR. A lot of how we move forward depends on what the future of the ECS release process looks like. Right now, we map ECS docs 1:1 to Stack docs. If that's changing, we'll need to rethink how we link to ECS documentation. I would set some time up to chat with your technical writer about potential next steps. |
Makes sense, and that is still being worked out. If we hold off on cleaning up the selectors for now, is it possible to keep ECS current at 8.11 for the time being? |
|
Hmm. That could potentially work. Wanna edit this PR and see what the checks say? That's the best way to test. |
|
@bmorelli25 looks like CI is happy with ecs current : 8.11 |
The team will not be releasing an ECS 8.12 while we decide how to approach releases of ECS going forward
I also cleared out some of the older versions from the live options.
Relates https://github.com/elastic/security-team/issues/8182