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

Migrate: STDIN prospector to the input interface #6116

Merged
merged 1 commit into from
Feb 3, 2018

Conversation

ph
Copy link
Contributor

@ph ph commented Jan 19, 2018

Use the input interface instead of the prospector.

Require: #6078

@ph ph added in progress Pull request is currently in progress. Filebeat Filebeat labels Jan 19, 2018
@ph ph mentioned this pull request Jan 19, 2018
10 tasks
@ph ph force-pushed the refactor/type-aliasing-input branch from d027f45 to 0e31dc7 Compare January 22, 2018 18:35
@ph ph force-pushed the refactor/stdin-prospector-to-input branch 2 times, most recently from ae13e57 to 382afee Compare January 23, 2018 02:30
@ph ph changed the base branch from refactor/type-aliasing-input to master January 23, 2018 02:30
@ph ph force-pushed the refactor/stdin-prospector-to-input branch from 382afee to 7ed96b2 Compare January 23, 2018 02:42
@ph ph added review and removed in progress Pull request is currently in progress. labels Jan 23, 2018
// Prospector is a prospector for stdin
type Prospector struct {
// Input is an input for stdin
type Input struct {
Copy link

Choose a reason for hiding this comment

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

is Input used in any other place? Let's not export symbols not required by other modules.

E.g. plugin types in libbeat outputs are not exported.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think its used outside like I've said when I have renamed the Prospector/input, I didn't revise any visibility I can certainly do a check on it, since all those PRs are small.

Copy link
Contributor

Choose a reason for hiding this comment

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

Let's do this in a second step as it will cause name conflicts in this PR.

I'm tempted to say there will be Inputs which use some part of an other Input.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

After giving some thinking I agree with @ruflin

@ruflin
Copy link
Contributor

ruflin commented Jan 25, 2018

@ph Can you rebase because of the CHANGELOG conflict?

@ph ph force-pushed the refactor/stdin-prospector-to-input branch from 7ed96b2 to 4e5a628 Compare January 30, 2018 21:08
@ph
Copy link
Contributor Author

ph commented Jan 30, 2018

@ruflin rebased.

@ph ph force-pushed the refactor/stdin-prospector-to-input branch from 4e5a628 to 0fbf3ad Compare January 31, 2018 14:20
@ruflin
Copy link
Contributor

ruflin commented Feb 1, 2018

@ph Sorry, needs rebase. I wonder if we should have a changelog entry for each migration or just one entry that links to the meta issue?

@ph
Copy link
Contributor Author

ph commented Feb 1, 2018 via email

@ph ph force-pushed the refactor/stdin-prospector-to-input branch from 0fbf3ad to bedda18 Compare February 2, 2018 15:39
@ruflin ruflin merged commit 436bbbc into elastic:master Feb 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants