Cherry-pick #19759 to 7.x: Send the config revision down to the endpoint application.#19802
Merged
ph merged 1 commit intoelastic:7.xfrom Jul 9, 2020
ph:backport_19759_7.x
Merged
Cherry-pick #19759 to 7.x: Send the config revision down to the endpoint application.#19802ph merged 1 commit intoelastic:7.xfrom ph:backport_19759_7.x
ph merged 1 commit intoelastic:7.xfrom
ph:backport_19759_7.x
Conversation
* Send the config revision down to the endpoint application. This PR make sure we forward the config revision down to the endpoint. (cherry picked from commit d03432b)
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
|
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
3 participants
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.
Cherry-pick of PR #19759 to 7.x branch. Original message:
What does this PR do?
This PR make sure we forward the config revision down to the endpoint.
Why is it important?
The endpoint uses that information to send information back to Elasticsearch.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs