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.

Sign up for GitHub

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

Jump to bottom

Specify an ECS version in Auditbeat/Packetbeat/Winlogbeat #19159

Merged
merged 2 commits into from
Jul 13, 2020
Merged

Specify an ECS version in Auditbeat/Packetbeat/Winlogbeat #19159

merged 2 commits into from
Jul 13, 2020

Commits on Jul 13, 2020

  1. Specify an ECS version in Auditbeat/Packetbeat/Winlogbeat 

    When we update the Beat (include all of its modules) we will then bump the ECS
version that it includes in events.

I went for a less granular approach than what is being used in Filebeat because
I think it's desirable to move a whole beat to a new ECS version "at once" and
more realistic to do so with these Beats that have fewer updates. By "at once" I
mean we won't release a version that is partially updated. This implies that if
we will be making multiple commits that we should use a feature branch to
ensure the update is atomic.

Closes elastic#17688
    @andrewkroh
    andrewkroh committed Jul 13, 2020
    Configuration menu
    Copy the full SHA
    ae6beb1 View commit details
    Browse the repository at this point in the history

  2. Fix imports

    @andrewkroh
    andrewkroh committed Jul 13, 2020
    Configuration menu
    Copy the full SHA
    12fb849 View commit details
    Browse the repository at this point in the history