-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Filebeat] Fix gcp/vpcflow module defaulting to file input #24719
Merged
andrewkroh
merged 2 commits into
elastic:master
from
andrewkroh:bugfix/fb/gcp-vpcflow-input
Mar 24, 2021
Merged
[Filebeat] Fix gcp/vpcflow module defaulting to file input #24719
andrewkroh
merged 2 commits into
elastic:master
from
andrewkroh:bugfix/fb/gcp-vpcflow-input
Mar 24, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
andrewkroh
added
bug
review
Filebeat
Filebeat
Team:Security-External Integrations
labels
Mar 23, 2021
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
botelastic
bot
added
needs_team
Indicates that the issue/PR needs a Team:* label
and removed
needs_team
Indicates that the issue/PR needs a Team:* label
labels
Mar 23, 2021
The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub
andrewkroh
force-pushed
the
bugfix/fb/gcp-vpcflow-input
branch
from
March 23, 2021 21:37
c12b5e8
to
ebf7888
Compare
andrewkroh
added
the
needs_backport
PR is waiting to be backported to other branches.
label
Mar 23, 2021
Collaborator
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
marc-gr
approved these changes
Mar 24, 2021
6 tasks
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this pull request
Mar 24, 2021
The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub (cherry picked from commit 4f91947)
andrewkroh
added
v7.13.0
and removed
needs_backport
PR is waiting to be backported to other branches.
labels
Mar 24, 2021
andrewkroh
added a commit
to andrewkroh/beats
that referenced
this pull request
Mar 24, 2021
The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub (cherry picked from commit 4f91947)
Merged
6 tasks
andrewkroh
added a commit
that referenced
this pull request
Mar 24, 2021
…ng to file input (#24733) The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub (cherry picked from commit 4f91947)
andrewkroh
added a commit
that referenced
this pull request
Mar 24, 2021
…ing to file input (#24734) The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub (cherry picked from commit 4f91947)
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…defaulting to file input (elastic#24734) The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest was not updated. As a result it's defaulting to the file input. This fixes the manifest. The workaround is to explicitly set the input type: vpcflow: enabled: true var.input: gcp-pubsub (cherry picked from commit c5ef8ed)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
The pubsub input was renamed from google-pubsub to gcp-pubsub and the vpcflow filesets manifest
was not updated. As a result it's defaulting to the file input. This fixes the manifest.
The workaround is to explicitly set the input type:
Why is it important?
The input won't start using existing configurations causing a breaking change.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Logs
Exiting: Failed to start crawler: starting input failed: Error while initializing input: No paths were defined for input accessing config