Cherry-pick #21285 to 7.x: Send snapshot flag together with metadata #21460
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 #21285 to 7.x branch. Original message:
What does this PR do?
For correct Source URI resolution fleet needs to be aware whether or not agent is a SNAPSHOT build or not.
This PR includes this information in two forms in
local
metadata which is sent duringenroll
andcheckin
elastic.agent.snapshot
- additional field set to true if agent is in snapshot modeelastic.agent.build.original
- long version info, in case of snapshot it will contain it e.g.8.0.0-SNAPSHOT (build: 3f1e3a5d016487f4cc995b019a846f3f13104f03 at 2020-09-24 08:57:34 +0000 UTC)
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.