Cherry-pick #19495 to 7.x: [Elastic Agent] Add changelog for breaking change in fleet.yml#19498
Merged
ph merged 1 commit intoelastic:7.xfrom Jun 29, 2020
Merged
Conversation
(cherry picked from commit 4286e1e)
Contributor
|
Pinging @elastic/ingest-management (Team:Ingest Management) |
ph
approved these changes
Jun 29, 2020
Contributor
|
merging this, only docs build could be affected by this. |
Contributor
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.
Cherry-pick of PR #19495 to 7.x branch. Original message:
What does this PR do?
Add entry into changelog for breaking the fleet.yml structure.
Why is it important?
To document that it was a breaking change.
Checklist
[ ] My code follows the style guidelines of this project[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.