-
Notifications
You must be signed in to change notification settings - Fork 431
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
Stage 1 Orchestrator RFC #1230
Stage 1 Orchestrator RFC #1230
Conversation
FYI the Metricbeat is working on this topic in parallel, see elastic/beats#17467 |
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 for moving this! Added some questions and suggestions.
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 for continuing to move this proposal forward, @ferozsalam! Excited to see all the discussions already taking place. 😃
Would you also update the target stage in the proposal: Stage: **1 (draft)**
?
Co-authored-by: Jaime Soriano Pastor <[email protected]>
@ebeahan I'm slightly confused by the latest build failures, which I think are caused by something in the test framework that needs updating. The error refers to a Golang file that I haven't touched:
This branch isn't missing any commits that are on master, and I've only touched the RFC Markdown, so I'm stumped. Any ideas? |
@ferozsalam Thanks for the mention, it's being investigated. The pass/fail isn't applicable to any changes made here, so don't worry about the test failures. |
Co-authored-by: Jaime Soriano Pastor <[email protected]>
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 good to me, thank you!!
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! LGTM
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.
The collaboration here has been fantastic! Thanks to @ferozsalam for all the iterations and to @jsoriano @kaiyan-sheng @ChrsMark for all the feedback.
I noticed one possible minor edit, but otherwise, I think the proposal looks great.
Next steps:
- It's been discussed out-of-band that @exekias will be acting as the sponsor here. I'll add @exekias to the
People
section when I update the advancement date. If this is incorrect, let me know. - The ECS team has found it useful to create a directory using the RFC number to capture examples and the proposed schema changes as standalone YML files (for use with
--include
). Just informational - no action required; I'll handle copy/pasting the YAML into that new file when I merge the proposal. - By advancing to stage 1, the
orchestrator.*
fields will be added to the experimental ECS schema. I'll also handle opening a separate PR for that implementation. - Once we merge this PR, I suggest creating the stage 2 PR shortly after even if the only change is updating the
stage
at the top of the document. It's great to already have the PR opened when thoughts or feedback come up.
f4352b0
Moving the orchestrator RFC from stage 0 into stage 1
Preview of markdown proposal