[Ingest Manager] Return ID when default output is found#75930
Merged
jen-huang merged 2 commits intoelastic:masterfrom Aug 26, 2020
Merged
[Ingest Manager] Return ID when default output is found#75930jen-huang merged 2 commits intoelastic:masterfrom
jen-huang merged 2 commits intoelastic:masterfrom
Conversation
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
💚 Build SucceededBuild metrics
History
To update your PR or re-run it, just comment with: |
skh
approved these changes
Aug 26, 2020
jen-huang
added a commit
to jen-huang/kibana
that referenced
this pull request
Aug 26, 2020
* Return ID when default output is found * Fix typing
jen-huang
added a commit
to jen-huang/kibana
that referenced
this pull request
Aug 26, 2020
* Return ID when default output is found * Fix typing
This file contains hidden or 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
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.
Summary
Fixes #75916, from #75916 (comment):
Unfortunately, I was not able to find a way to reproduce the original behavior. We improved setup handling recently (#75372) so it's possible that this behavior was fixed (or occurrence reduced) as a side effect of those those general improvements. Either way, it's still good to fix the code logic here.