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

Update fields.yml for ECS v1.1.0 #13321

Merged
merged 2 commits into from
Aug 24, 2019

Conversation

andrewkroh
Copy link
Member

This updates the fields.ecs.yml file and the vendored Go code to be based on ECS v1.1.0.

Relates #13320

@elasticmachine
Copy link
Collaborator

Pinging @elastic/siem

Copy link
Contributor

@adriansr adriansr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@webmat webmat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor nit and one question, but LGTM

CHANGELOG.next.asciidoc Outdated Show resolved Hide resolved
@webmat
Copy link
Contributor

webmat commented Aug 23, 2019

Are we having big problems on Jenkins? Let's try to kick it again, just for kicks.

jenkins, test this

This updates the fields.ecs.yml file and the vendored Go code to be based on ECS v1.1.0.

Relates elastic#13320
@andrewkroh andrewkroh force-pushed the feature/ecs-1-1-0-schema branch from 330486e to f578a59 Compare August 23, 2019 17:59
@@ -20,4 +20,4 @@
package ecs

// Version is the Elastic Common Schema version from which this was generated.
const Version = "1.0.1"
const Version = "1.1.0"
Copy link
Contributor

@webmat webmat Aug 23, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@andrewkroh Will the events have ecs.version=1.1.0 based on this? Or is there another constant to be changed somewhere?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had done a grep for 1.0.1 in libbeat and didn't find anything so it must be using a constant. We can double check this after we have a build.

@andrewkroh
Copy link
Member Author

There's a failure in x-pack/metricbeat but it's passing on Jenkins. And on Jenkins all of the Windows workers are failing due to some kind Jenkins problem with archiving artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants