From 5736dcce1bb3c6969d53b0cc803afabebc9a8b2b Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 20:50:22 +0100 Subject: [PATCH 1/7] V2 Changelog: adding fragments for visible changes --- .../1665780486-heartbeat-es-output-only.yaml | 2 +- .../1666095433-service_runtime_v2.yaml | 4 +-- ...for-running-the-elastic-agent-shipper.yaml | 4 +-- ...1668483030-common-expression-language.yaml | 2 +- .../1668645651-apm-fleet-config.yaml | 6 ++-- ...1669066497-struct-compare-unit-update.yaml | 6 ++-- ...669159455-reimplement-processes-route.yaml | 6 ++-- ...pawned-components-to-simplify-logging.yaml | 4 +-- ...-action-ack-crash-after-local-upgrade.yaml | 4 +-- ...-url-directory-created-for-monitoring.yaml | 6 ++-- ...and-osquery-extension.ext-permissions.yaml | 4 +-- ...-logging-level-to-fleet-configuration.yaml | 4 +-- ...tition-occurs-from-a-dynamic-provider.yaml | 4 +-- ...669929902-fix-local-fleet-server-port.yaml | 6 ++-- ...e-inputs-when-all-streams-are-removed.yaml | 4 +-- ...art-Elastic-Agent-on-log-level-change.yaml | 4 +-- .../1672911992-v2-control-protocol.yaml | 33 ++++++++++++++++++ .../fragments/1672911993-v2-directory.yaml | 33 ++++++++++++++++++ .../fragments/1672911994-v2-packaging.yaml | 32 +++++++++++++++++ .../fragments/1672911995-v2-diagnostic.yaml | 34 +++++++++++++++++++ .../fragments/1672911997-v2-inspect.yaml | 32 +++++++++++++++++ .../1672911999-v2-health-status.yaml | 32 +++++++++++++++++ ...001-fix-duplicate-entries-on-upgrade.yaml} | 21 +++++------- 23 files changed, 240 insertions(+), 47 deletions(-) create mode 100644 changelog/fragments/1672911992-v2-control-protocol.yaml create mode 100644 changelog/fragments/1672911993-v2-directory.yaml create mode 100644 changelog/fragments/1672911994-v2-packaging.yaml create mode 100644 changelog/fragments/1672911995-v2-diagnostic.yaml create mode 100644 changelog/fragments/1672911997-v2-inspect.yaml create mode 100644 changelog/fragments/1672911999-v2-health-status.yaml rename changelog/fragments/{1668591286-fix-beats-logs.yaml => 1672912001-fix-duplicate-entries-on-upgrade.yaml} (71%) diff --git a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml b/changelog/fragments/1665780486-heartbeat-es-output-only.yaml index 1e3b4059ddf..c8a9a0e6962 100644 --- a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml +++ b/changelog/fragments/1665780486-heartbeat-es-output-only.yaml @@ -24,7 +24,7 @@ component: synthetics-integration # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1491 +pr: https://github.com/elastic/elastic-agent/pull/1491 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. diff --git a/changelog/fragments/1666095433-service_runtime_v2.yaml b/changelog/fragments/1666095433-service_runtime_v2.yaml index f54aa7e5d9c..25d5067fb8c 100644 --- a/changelog/fragments/1666095433-service_runtime_v2.yaml +++ b/changelog/fragments/1666095433-service_runtime_v2.yaml @@ -1,5 +1,5 @@ kind: feature summary: Service runtime for V2 description: Service runtime for V2, tailored specifically for Endpoint service. -pr: 1529 -issue: 1069 +pr: https://github.com/elastic/elastic-agent/pull/1529 +issue: https://github.com/elastic/elastic-agent/issues/1069 diff --git a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml b/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml index 26430b05741..718aef05879 100644 --- a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml +++ b/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1527 +pr: https://github.com/elastic/elastic-agent/pull/1527 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 219 +issue: https://github.com/elastic/elastic-agent/issues/219 diff --git a/changelog/fragments/1668483030-common-expression-language.yaml b/changelog/fragments/1668483030-common-expression-language.yaml index 824d7f5a501..0391c624f30 100644 --- a/changelog/fragments/1668483030-common-expression-language.yaml +++ b/changelog/fragments/1668483030-common-expression-language.yaml @@ -24,7 +24,7 @@ component: spec # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1719 +pr: https://github.com/elastic/elastic-agent/pull/1719 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. diff --git a/changelog/fragments/1668645651-apm-fleet-config.yaml b/changelog/fragments/1668645651-apm-fleet-config.yaml index 1e7738f43af..7db14c6f0d3 100644 --- a/changelog/fragments/1668645651-apm-fleet-config.yaml +++ b/changelog/fragments/1668645651-apm-fleet-config.yaml @@ -11,7 +11,7 @@ kind: bug-fix # Change summary; a 80ish characters long description of the change. -summary: V2 Provide fleet configuration to APM server +summary: V2 Provide Fleet configuration to APM server # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -# pr: 1234 +pr: https://github.com/elastic/elastic-agent/pull/1745 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1737 +issue: https://github.com/elastic/elastic-agent/issues/1737 diff --git a/changelog/fragments/1669066497-struct-compare-unit-update.yaml b/changelog/fragments/1669066497-struct-compare-unit-update.yaml index b907a4dd97d..1428aab2629 100644 --- a/changelog/fragments/1669066497-struct-compare-unit-update.yaml +++ b/changelog/fragments/1669066497-struct-compare-unit-update.yaml @@ -11,7 +11,7 @@ kind: bug-fix # Change summary; a 80ish characters long description of the change. -summary: change config comparison to fix false unit update events +summary: Change config comparison to fix false unit update events # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. @@ -24,8 +24,8 @@ component: runtime # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1766 +pr: https://github.com/elastic/elastic-agent/pull/1766 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1738 +issue: https://github.com/elastic/elastic-agent/issues/1738 diff --git a/changelog/fragments/1669159455-reimplement-processes-route.yaml b/changelog/fragments/1669159455-reimplement-processes-route.yaml index 574fdeedf83..aaa00ef715d 100644 --- a/changelog/fragments/1669159455-reimplement-processes-route.yaml +++ b/changelog/fragments/1669159455-reimplement-processes-route.yaml @@ -11,7 +11,7 @@ kind: feature # Change summary; a 80ish characters long description of the change. -summary: reimplement processes route +summary: Reimplement processes route # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1773 +pr: https://github.com/elastic/elastic-agent/pull/1773 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1731 +issue: https://github.com/elastic/elastic-agent/issues/1731 diff --git a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml b/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml index 8dfa6a9aa2f..a20cfea270b 100644 --- a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml +++ b/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1702 +pr: https://github.com/elastic/elastic-agent/pull/1702 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 221 +issue: https://github.com/elastic/elastic-agent/issues/221 diff --git a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml b/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml index a4bce27d801..083347ef366 100644 --- a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml +++ b/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1805 +pr: https://github.com/elastic/elastic-agent/pull/1805 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1788 +issue: https://github.com/elastic/elastic-agent/issues/1788 diff --git a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml b/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml index dbb33904f23..3b3b899ebc9 100644 --- a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml +++ b/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml @@ -11,7 +11,7 @@ kind: bug-fix # Change summary; a 80ish characters long description of the change. -summary: fix erroneous http url directory created for monitoring +summary: Fix erroneous http url directory created for monitoring # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1811 +pr: https://github.com/elastic/elastic-agent/pull/1811 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 +issue: https://github.com/elastic/elastic-agent/issues/1806 diff --git a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml b/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml index b97530312d4..09dc99a0d4e 100644 --- a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml +++ b/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml @@ -8,7 +8,7 @@ # - security: impacts on the security of a product or a user’s deployment. # - upgrade: important information for someone upgrading from a prior version # - other: does not fit into any of the other categories -kind: feature +kind: bug-fix # Change summary; a 80ish characters long description of the change. summary: Fix osqueryd and osquery-extension.ext permissions @@ -24,7 +24,7 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1829 +pr: https://github.com/elastic/elastic-agent/pull/1829 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. diff --git a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml b/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml index c693e26a7f5..cd3bb7e6383 100644 --- a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml +++ b/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1856 +pr: https://github.com/elastic/elastic-agent/pull/1856 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1853 +issue: https://github.com/elastic/elastic-agent/issues/1853 diff --git a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml b/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml index f903beb0c11..5af9a9c9b1a 100644 --- a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml +++ b/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1866 +pr: https://github.com/elastic/elastic-agent/pull/1866 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1751 +issue: https://github.com/elastic/elastic-agent/issues/1751 diff --git a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml b/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml index 08119ec5ac6..250d4373ba0 100644 --- a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml +++ b/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml @@ -11,7 +11,7 @@ kind: bug-fix # Change summary; a 80ish characters long description of the change. -summary: elastic-agent will use local port when running fleet-server +summary: Elastic-agent will use local port when running fleet-server # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -#pr: 1234 +pr: https://github.com/elastic/elastic-agent/pull/1867 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 +issue: https://github.com/elastic/ingest-dev/issues/1394 diff --git a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml b/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml index 070cb9a6f52..240cb753106 100644 --- a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml +++ b/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1869 +pr: https://github.com/elastic/elastic-agent/pull/1869 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: 1868 +issue: https://github.com/elastic/elastic-agent/issues/1868 diff --git a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml b/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml index 94de9883c23..b84d7621212 100644 --- a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml +++ b/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml @@ -24,8 +24,8 @@ component: # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1914 +pr: https://github.com/elastic/elastic-agent/pull/1914 # Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 +issue: https://github.com/elastic/elastic-agent/issues/1896 diff --git a/changelog/fragments/1672911992-v2-control-protocol.yaml b/changelog/fragments/1672911992-v2-control-protocol.yaml new file mode 100644 index 00000000000..59936803cfc --- /dev/null +++ b/changelog/fragments/1672911992-v2-control-protocol.yaml @@ -0,0 +1,33 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: breaking-change + +# Change summary; a 80ish characters long description of the change. +summary: | + New control protocol between the Elastic Agent and its subprocesses. + Enables per integration health reporting and simplifies new input development, among other things. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/elastic-agent/pull/1701 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/836 \ No newline at end of file diff --git a/changelog/fragments/1672911993-v2-directory.yaml b/changelog/fragments/1672911993-v2-directory.yaml new file mode 100644 index 00000000000..992c10bbcaa --- /dev/null +++ b/changelog/fragments/1672911993-v2-directory.yaml @@ -0,0 +1,33 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: upgrade + +# Change summary; a 80ish characters long description of the change. +summary: | + Internal directory structure change: addition of the components directory + (and removal of the downloads directory) to contain binaries and their associated artifacts. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/elastic-agent/pull/1701 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911994-v2-packaging.yaml b/changelog/fragments/1672911994-v2-packaging.yaml new file mode 100644 index 00000000000..729107e3d6d --- /dev/null +++ b/changelog/fragments/1672911994-v2-packaging.yaml @@ -0,0 +1,32 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: upgrade + +# Change summary; a 80ish characters long description of the change. +summary: | + All binaries for every supported integration will be bundled in the Elastic Agent by default. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/elastic-agent-shipper/pull/126 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911995-v2-diagnostic.yaml b/changelog/fragments/1672911995-v2-diagnostic.yaml new file mode 100644 index 00000000000..d411ab81806 --- /dev/null +++ b/changelog/fragments/1672911995-v2-diagnostic.yaml @@ -0,0 +1,34 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: breaking-change + +# Change summary; a 80ish characters long description of the change. +summary: | + Diagnostic: --pprof argument has been removed, it's now always provided. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +description: | + The diagnostic command is gathering diagnostic information about the Elastic Agent and each + component/unit ran by the Elastic Agent. --pprof argument has been removed: it's now always provided. + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/elastic-agent/pull/1140 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911997-v2-inspect.yaml b/changelog/fragments/1672911997-v2-inspect.yaml new file mode 100644 index 00000000000..6ecaad07077 --- /dev/null +++ b/changelog/fragments/1672911997-v2-inspect.yaml @@ -0,0 +1,32 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: feature + +# Change summary; a 80ish characters long description of the change. +summary: | + Add inspect components command to inspect the computed components/units model of the current configuration (elastic-agent inspect components). + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/elastic-agent/pull/1701 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911999-v2-health-status.yaml b/changelog/fragments/1672911999-v2-health-status.yaml new file mode 100644 index 00000000000..ab1d29d383d --- /dev/null +++ b/changelog/fragments/1672911999-v2-health-status.yaml @@ -0,0 +1,32 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: enhancement + +# Change summary; a 80ish characters long description of the change. +summary: | + Health Status: Elastic Agent now indicates detailed status information for each component/unit. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: agent + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +pr: https://github.com/elastic/fleet-server/pull/1747 + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/100 diff --git a/changelog/fragments/1668591286-fix-beats-logs.yaml b/changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml similarity index 71% rename from changelog/fragments/1668591286-fix-beats-logs.yaml rename to changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml index b9f749b12dc..99e9c2fb81a 100644 --- a/changelog/fragments/1668591286-fix-beats-logs.yaml +++ b/changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml @@ -11,26 +11,23 @@ kind: bug-fix # Change summary; a 80ish characters long description of the change. -summary: "monitoring: fix JSON logs parsing for Beats" +summary: | + Correctly preserve the Filebeat registry and other persistent input state during upgrades. + Eliminates event duplication after Elastic agent upgrades. # Long description; in case the summary is not enough to describe the change # this field accommodate a description without length limits. -description: >- - Fixes the JSON parsing from Beats logs. The configuration sent to - Filebeat did not contain the input type, hence a log input instead of a - filestream one was being started. - - This commit also improves the configuraiton of the ndjson parser. +# description: # Affected component; a word indicating the component this changeset affects. -component: monitoring +component: agent -# PR number; optional; the PR number that added the changeset. +# PR URL; optional; the PR number that added the changeset. # If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. # NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. # Please provide it if you are adding a fragment for a different PR. -pr: 1735 +pr: https://github.com/elastic/elastic-agent/pull/1701 -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). # If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 +issue: https://github.com/elastic/elastic-agent/issues/836 From 14f492957fb0f4f5c949816fe1c9ef7620fb5598 Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 20:54:25 +0100 Subject: [PATCH 2/7] Known issue about osquery --- .../1672912002-osquery-known-issue.yaml | 32 +++++++++++++++++++ 1 file changed, 32 insertions(+) create mode 100644 changelog/fragments/1672912002-osquery-known-issue.yaml diff --git a/changelog/fragments/1672912002-osquery-known-issue.yaml b/changelog/fragments/1672912002-osquery-known-issue.yaml new file mode 100644 index 00000000000..f02f48a299f --- /dev/null +++ b/changelog/fragments/1672912002-osquery-known-issue.yaml @@ -0,0 +1,32 @@ +# Kind can be one of: +# - breaking-change: a change to previously-documented behavior +# - deprecation: functionality that is being removed in a later release +# - bug-fix: fixes a problem in a previous version +# - enhancement: extends functionality but does not break or fix existing behavior +# - feature: new functionality +# - known-issue: problems that we are aware of in a given version +# - security: impacts on the security of a product or a user’s deployment. +# - upgrade: important information for someone upgrading from a prior version +# - other: does not fit into any of the other categories +kind: known-issue + +# Change summary; a 80ish characters long description of the change. +summary: | + OSQuery live query results can take up to 5 mins to show up in Kibana + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# description: + +# Affected component; a word indicating the component this changeset affects. +component: osquery + +# PR URL; optional; the PR number that added the changeset. +# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. +# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. +# Please provide it if you are adding a fragment for a different PR. +#pr: + +# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). +# If not present is automatically filled by the tooling with the issue linked to the PR number. +issue: https://github.com/elastic/elastic-agent/issues/2066 From a6c7b9605e8faf06d56476e17d63899630285b56 Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 21:12:35 +0100 Subject: [PATCH 3/7] Consolidated changelog + cleanup --- changelog/8.6.0.yaml | 330 ++++++++++++++++++ .../1665780486-heartbeat-es-output-only.yaml | 31 -- .../1666095433-service_runtime_v2.yaml | 5 - .../1667243040-Upgrade-node-to-18.12.0.yaml | 31 -- ...for-running-the-elastic-agent-shipper.yaml | 31 -- ...1668483030-common-expression-language.yaml | 31 -- .../1668645651-apm-fleet-config.yaml | 31 -- .../fragments/1668679987-apm-monitoring.yaml | 31 -- ...1669066497-struct-compare-unit-update.yaml | 31 -- ...669159455-reimplement-processes-route.yaml | 31 -- ...pawned-components-to-simplify-logging.yaml | 31 -- ...-action-ack-crash-after-local-upgrade.yaml | 31 -- ...-url-directory-created-for-monitoring.yaml | 31 -- ...and-osquery-extension.ext-permissions.yaml | 31 -- ...-logging-level-to-fleet-configuration.yaml | 31 -- ...tition-occurs-from-a-dynamic-provider.yaml | 31 -- ...669929902-fix-local-fleet-server-port.yaml | 31 -- ...e-inputs-when-all-streams-are-removed.yaml | 31 -- ...art-Elastic-Agent-on-log-level-change.yaml | 31 -- .../1671748292-input-ids-are-required.yaml | 34 -- .../1672911992-v2-control-protocol.yaml | 33 -- .../fragments/1672911993-v2-directory.yaml | 33 -- .../fragments/1672911994-v2-packaging.yaml | 32 -- .../fragments/1672911995-v2-diagnostic.yaml | 34 -- .../fragments/1672911997-v2-inspect.yaml | 32 -- .../1672911999-v2-health-status.yaml | 32 -- ...2001-fix-duplicate-entries-on-upgrade.yaml | 33 -- .../1672912002-osquery-known-issue.yaml | 32 -- 28 files changed, 330 insertions(+), 827 deletions(-) create mode 100644 changelog/8.6.0.yaml delete mode 100644 changelog/fragments/1665780486-heartbeat-es-output-only.yaml delete mode 100644 changelog/fragments/1666095433-service_runtime_v2.yaml delete mode 100644 changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml delete mode 100644 changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml delete mode 100644 changelog/fragments/1668483030-common-expression-language.yaml delete mode 100644 changelog/fragments/1668645651-apm-fleet-config.yaml delete mode 100644 changelog/fragments/1668679987-apm-monitoring.yaml delete mode 100644 changelog/fragments/1669066497-struct-compare-unit-update.yaml delete mode 100644 changelog/fragments/1669159455-reimplement-processes-route.yaml delete mode 100644 changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml delete mode 100644 changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml delete mode 100644 changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml delete mode 100644 changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml delete mode 100644 changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml delete mode 100644 changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml delete mode 100644 changelog/fragments/1669929902-fix-local-fleet-server-port.yaml delete mode 100644 changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml delete mode 100644 changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml delete mode 100644 changelog/fragments/1671748292-input-ids-are-required.yaml delete mode 100644 changelog/fragments/1672911992-v2-control-protocol.yaml delete mode 100644 changelog/fragments/1672911993-v2-directory.yaml delete mode 100644 changelog/fragments/1672911994-v2-packaging.yaml delete mode 100644 changelog/fragments/1672911995-v2-diagnostic.yaml delete mode 100644 changelog/fragments/1672911997-v2-inspect.yaml delete mode 100644 changelog/fragments/1672911999-v2-health-status.yaml delete mode 100644 changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml delete mode 100644 changelog/fragments/1672912002-osquery-known-issue.yaml diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml new file mode 100644 index 00000000000..1ef8e83a75d --- /dev/null +++ b/changelog/8.6.0.yaml @@ -0,0 +1,330 @@ +version: 8.6.0 +entries: + - kind: feature + summary: Only support elasticsearch as an output for the beta synthetics integration. + description: "" + component: synthetics-integration + pr: + - https://github.com/elastic/elastic-agent/pull/1491 + issue: [] + timestamp: 1665780486 + file: + name: 1665780486-heartbeat-es-output-only.yaml + checksum: 361f993ba3220aef531f7949308e61d2cbf82e03 + - kind: feature + summary: Service runtime for V2 + description: Service runtime for V2, tailored specifically for Endpoint service. + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1529 + issue: + - https://github.com/elastic/elastic-agent/issues/1069 + timestamp: 1666095433 + file: + name: 1666095433-service_runtime_v2.yaml + checksum: 94f777454bf571caf8da848441c43eb6d7b3bc10 + - kind: feature + summary: Upgrade node to 18.12.0 + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1657 + issue: [] + timestamp: 1667243040 + file: + name: 1667243040-Upgrade-node-to-18.12.0.yaml + checksum: 38b5473e0ee1165ad9c5d74ee969a9228c3fa68a + - kind: feature + summary: Add experimental support for running the elastic-agent-shipper + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1527 + issue: + - https://github.com/elastic/elastic-agent/issues/219 + timestamp: 1667571017 + file: + name: 1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml + checksum: b2f5a0a8f9933c9ee624457116295aa674ef2a23 + - kind: feature + summary: Add Common Expression Language input mapping to the Filebeat spec. + description: "" + component: spec + pr: + - https://github.com/elastic/elastic-agent/pull/1719 + issue: [] + timestamp: 1668483030 + file: + name: 1668483030-common-expression-language.yaml + checksum: 82427fc514372c067e140837177c8d81131ed424 + - kind: bug-fix + summary: V2 Provide Fleet configuration to APM server + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1745 + issue: + - https://github.com/elastic/elastic-agent/issues/1737 + timestamp: 1668645651 + file: + name: 1668645651-apm-fleet-config.yaml + checksum: ce8dc3cc4c598555ef05bfa0aa4f8daf0ac680b2 + - kind: bug-fix + summary: apm-monitoring + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1748 + issue: [] + timestamp: 1668679987 + file: + name: 1668679987-apm-monitoring.yaml + checksum: ef78089de487eeea3728f872de9d544bdecf1c5b + - kind: bug-fix + summary: Change config comparison to fix false unit update events + description: "" + component: runtime + pr: + - https://github.com/elastic/elastic-agent/pull/1766 + issue: + - https://github.com/elastic/elastic-agent/issues/1738 + timestamp: 1669066497 + file: + name: 1669066497-struct-compare-unit-update.yaml + checksum: 513333eb8795e990ef632df7e2b71120feeaf892 + - kind: feature + summary: Reimplement processes route + description: Re-implement processes route to restore compatibility with the current cloud health checks + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1773 + issue: + - https://github.com/elastic/elastic-agent/issues/1731 + timestamp: 1669159455 + file: + name: 1669159455-reimplement-processes-route.yaml + checksum: cbeb5b5766bf733dd5e200a69353e326c642a971 + - kind: feature + summary: Capture stdout/stderr of all spawned components and adjust default log level to info for all components + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1702 + issue: + - https://github.com/elastic/elastic-agent/issues/221 + timestamp: 1669236059 + file: + name: 1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml + checksum: b4cf9cff0ef13bd168cadc80f89c4969b49fb378 + - kind: bug-fix + summary: Fix Elastic-Agent fails to re-start during upgrade + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1805 + issue: + - https://github.com/elastic/elastic-agent/issues/1788 + timestamp: 1669665017 + file: + name: 1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml + checksum: 80fb772957944cd3687aa999595d6be1b4d96d2a + - kind: bug-fix + summary: Fix erroneous http url directory created for monitoring + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1811 + issue: + - https://github.com/elastic/elastic-agent/issues/1806 + timestamp: 1669668741 + file: + name: 1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml + checksum: d2c3b670e658413f5aa3bd650d79900dc7bc720a + - kind: bug-fix + summary: Fix osqueryd and osquery-extension.ext permissions + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1829 + issue: [] + timestamp: 1669739947 + file: + name: 1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml + checksum: cc8d9c7ab91b7e4c45a11b5b1347238d3e757453 + - kind: feature + summary: Add agent logging level to fleet configuration + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1856 + issue: + - https://github.com/elastic/elastic-agent/issues/1853 + timestamp: 1669845868 + file: + name: 1669845868-add-agent-logging-level-to-fleet-configuration.yaml + checksum: 33cbf01b52f8cf30971d84fadbba10163197fe61 + - kind: feature + summary: Ensure unique input ID when variable substition occurs from a dynamic provider + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1866 + issue: + - https://github.com/elastic/elastic-agent/issues/1751 + timestamp: 1669928791 + file: + name: 1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml + checksum: c057e4c3420b9549dc31c8e13e58ad3992a8eb49 + - kind: bug-fix + summary: Elastic-agent will use local port when running fleet-server + description: The elastic-agent will now use the 8221 locally bound port when running fleet-server instead of the external port (8220). + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1867 + issue: + - https://github.com/elastic/ingest-dev/issues/1394 + timestamp: 1669929902 + file: + name: 1669929902-fix-local-fleet-server-port.yaml + checksum: 94f37fd1ff74bd320ec25cfcf2e2a0890eda494a + - kind: feature + summary: Remove inputs when all streams are removed + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1869 + issue: + - https://github.com/elastic/elastic-agent/issues/1868 + timestamp: 1669940990 + file: + name: 1669940990-Remove-inputs-when-all-streams-are-removed.yaml + checksum: 3fcf26a5bbb988db85c0c5923d4bd2284dc95866 + - kind: feature + summary: No longer restart Elastic Agent on log level change + description: "" + component: "" + pr: + - https://github.com/elastic/elastic-agent/pull/1914 + issue: + - https://github.com/elastic/elastic-agent/issues/1896 + timestamp: 1670518841 + file: + name: 1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml + checksum: 12b34904cd47182a45e6e113518ef91ec718ebac + - kind: breaking-change + summary: Each input in an agent policy must have a unique ID. + description: | + Each input in an agent policy must have a unique ID, like "id: my-unique-input-id". + This only affects standalone agents. Unique IDs are automatically generated in + agent policies managed by Fleet. + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1994 + issue: [] + timestamp: 1671748292 + file: + name: 1671748292-input-ids-are-required.yaml + checksum: 3ca6d7c10ce16c72c74b67b18916407ad09459fd + - kind: breaking-change + summary: "New control protocol between the Elastic Agent and its subprocesses. \nEnables per integration health reporting and simplifies new input development, among other things.\n" + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1701 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672911992 + file: + name: 1672911992-v2-control-protocol.yaml + checksum: 837bf1d3f02ab63b94b5fbe5853b8163aaeb6f31 + - kind: upgrade + summary: "Internal directory structure change: addition of the components directory \n(and removal of the downloads directory) to contain binaries and their associated artifacts.\n" + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1701 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672911993 + file: + name: 1672911993-v2-directory.yaml + checksum: 6ab87446b15a94993186754952e08c00a72c13ba + - kind: upgrade + summary: | + All binaries for every supported integration will be bundled in the Elastic Agent by default. + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent-shipper/pull/126 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672911994 + file: + name: 1672911994-v2-packaging.yaml + checksum: b6ae49ca5e99b94901d9585d1c21d326065a5cc6 + - kind: breaking-change + summary: | + Diagnostic: --pprof argument has been removed, it's now always provided. + description: | + The diagnostic command is gathering diagnostic information about the Elastic Agent and each + component/unit ran by the Elastic Agent. --pprof argument has been removed: it's now always provided. + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1140 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672911995 + file: + name: 1672911995-v2-diagnostic.yaml + checksum: 2ca011d608585e5b81446389da7590c0aecada7b + - kind: feature + summary: | + Add inspect components command to inspect the computed components/units model of the current configuration (elastic-agent inspect components). + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1701 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672911997 + file: + name: 1672911997-v2-inspect.yaml + checksum: 464bdde8aaadcd25590b89165d32131f4a4b168c + - kind: enhancement + summary: | + Health Status: Elastic Agent now indicates detailed status information for each component/unit. + description: "" + component: agent + pr: + - https://github.com/elastic/fleet-server/pull/1747 + issue: + - https://github.com/elastic/elastic-agent/issues/100 + timestamp: 1672911999 + file: + name: 1672911999-v2-health-status.yaml + checksum: eeb54c42273e877893abda9f56a92c2d31c4fa46 + - kind: bug-fix + summary: "Correctly preserve the Filebeat registry and other persistent input state during upgrades. \nEliminates event duplication after Elastic agent upgrades.\n" + description: "" + component: agent + pr: + - https://github.com/elastic/elastic-agent/pull/1701 + issue: + - https://github.com/elastic/elastic-agent/issues/836 + timestamp: 1672912001 + file: + name: 1672912001-fix-duplicate-entries-on-upgrade.yaml + checksum: 4a06860accf7fcbae88034b9aaf669445071168e + - kind: known-issue + summary: | + OSQuery live query results can take up to 5 mins to show up in Kibana + description: "" + component: osquery + pr: + - https://github.com/elastic/elastic-agent/pull/2076 + issue: + - https://github.com/elastic/elastic-agent/issues/2066 + timestamp: 1672912002 + file: + name: 1672912002-osquery-known-issue.yaml + checksum: e0f4d4d25322bd42298f080c62f9a86c361e7af1 diff --git a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml b/changelog/fragments/1665780486-heartbeat-es-output-only.yaml deleted file mode 100644 index c8a9a0e6962..00000000000 --- a/changelog/fragments/1665780486-heartbeat-es-output-only.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Only support elasticsearch as an output for the beta synthetics integration. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: synthetics-integration - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1491 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 diff --git a/changelog/fragments/1666095433-service_runtime_v2.yaml b/changelog/fragments/1666095433-service_runtime_v2.yaml deleted file mode 100644 index 25d5067fb8c..00000000000 --- a/changelog/fragments/1666095433-service_runtime_v2.yaml +++ /dev/null @@ -1,5 +0,0 @@ -kind: feature -summary: Service runtime for V2 -description: Service runtime for V2, tailored specifically for Endpoint service. -pr: https://github.com/elastic/elastic-agent/pull/1529 -issue: https://github.com/elastic/elastic-agent/issues/1069 diff --git a/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml b/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml deleted file mode 100644 index a670ebab9cb..00000000000 --- a/changelog/fragments/1667243040-Upgrade-node-to-18.12.0.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Upgrade node to 18.12.0 - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: 1234 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 diff --git a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml b/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml deleted file mode 100644 index 718aef05879..00000000000 --- a/changelog/fragments/1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Add experimental support for running the elastic-agent-shipper - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1527 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/219 diff --git a/changelog/fragments/1668483030-common-expression-language.yaml b/changelog/fragments/1668483030-common-expression-language.yaml deleted file mode 100644 index 0391c624f30..00000000000 --- a/changelog/fragments/1668483030-common-expression-language.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Add Common Expression Language input mapping to the Filebeat spec. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: spec - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1719 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 diff --git a/changelog/fragments/1668645651-apm-fleet-config.yaml b/changelog/fragments/1668645651-apm-fleet-config.yaml deleted file mode 100644 index 7db14c6f0d3..00000000000 --- a/changelog/fragments/1668645651-apm-fleet-config.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: V2 Provide Fleet configuration to APM server - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1745 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1737 diff --git a/changelog/fragments/1668679987-apm-monitoring.yaml b/changelog/fragments/1668679987-apm-monitoring.yaml deleted file mode 100644 index fed7afe9177..00000000000 --- a/changelog/fragments/1668679987-apm-monitoring.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: apm-monitoring - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: 1234 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 diff --git a/changelog/fragments/1669066497-struct-compare-unit-update.yaml b/changelog/fragments/1669066497-struct-compare-unit-update.yaml deleted file mode 100644 index 1428aab2629..00000000000 --- a/changelog/fragments/1669066497-struct-compare-unit-update.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Change config comparison to fix false unit update events - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: runtime - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1766 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1738 diff --git a/changelog/fragments/1669159455-reimplement-processes-route.yaml b/changelog/fragments/1669159455-reimplement-processes-route.yaml deleted file mode 100644 index aaa00ef715d..00000000000 --- a/changelog/fragments/1669159455-reimplement-processes-route.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Reimplement processes route - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: Re-implement processes route to restore compatibility with the current cloud health checks - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1773 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1731 diff --git a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml b/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml deleted file mode 100644 index a20cfea270b..00000000000 --- a/changelog/fragments/1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Capture stdout/stderr of all spawned components and adjust default log level to info for all components - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1702 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/221 diff --git a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml b/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml deleted file mode 100644 index 083347ef366..00000000000 --- a/changelog/fragments/1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Fix Elastic-Agent fails to re-start during upgrade - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1805 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1788 diff --git a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml b/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml deleted file mode 100644 index 3b3b899ebc9..00000000000 --- a/changelog/fragments/1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Fix erroneous http url directory created for monitoring - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1811 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1806 diff --git a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml b/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml deleted file mode 100644 index 09dc99a0d4e..00000000000 --- a/changelog/fragments/1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Fix osqueryd and osquery-extension.ext permissions - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1829 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: 1234 diff --git a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml b/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml deleted file mode 100644 index cd3bb7e6383..00000000000 --- a/changelog/fragments/1669845868-add-agent-logging-level-to-fleet-configuration.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Add agent logging level to fleet configuration - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1856 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1853 diff --git a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml b/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml deleted file mode 100644 index 5af9a9c9b1a..00000000000 --- a/changelog/fragments/1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Ensure unique input ID when variable substition occurs from a dynamic provider - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1866 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1751 diff --git a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml b/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml deleted file mode 100644 index 250d4373ba0..00000000000 --- a/changelog/fragments/1669929902-fix-local-fleet-server-port.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: Elastic-agent will use local port when running fleet-server - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: The elastic-agent will now use the 8221 locally bound port when running fleet-server instead of the external port (8220). - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1867 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/ingest-dev/issues/1394 diff --git a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml b/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml deleted file mode 100644 index 240cb753106..00000000000 --- a/changelog/fragments/1669940990-Remove-inputs-when-all-streams-are-removed.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: Remove inputs when all streams are removed - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1869 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1868 diff --git a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml b/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml deleted file mode 100644 index b84d7621212..00000000000 --- a/changelog/fragments/1670518841-No-longer-restart-Elastic-Agent-on-log-level-change.yaml +++ /dev/null @@ -1,31 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: No longer restart Elastic Agent on log level change - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -#description: - -# Affected component; a word indicating the component this changeset affects. -component: - -# PR number; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1914 - -# Issue number; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/1896 diff --git a/changelog/fragments/1671748292-input-ids-are-required.yaml b/changelog/fragments/1671748292-input-ids-are-required.yaml deleted file mode 100644 index b14524c4352..00000000000 --- a/changelog/fragments/1671748292-input-ids-are-required.yaml +++ /dev/null @@ -1,34 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: Each input in an agent policy must have a unique ID. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: | - Each input in an agent policy must have a unique ID, like "id: my-unique-input-id". - This only affects standalone agents. Unique IDs are automatically generated in - agent policies managed by Fleet. - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: https://github.com/owner/repo/1234 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -#issue: https://github.com/owner/repo/1234 diff --git a/changelog/fragments/1672911992-v2-control-protocol.yaml b/changelog/fragments/1672911992-v2-control-protocol.yaml deleted file mode 100644 index 59936803cfc..00000000000 --- a/changelog/fragments/1672911992-v2-control-protocol.yaml +++ /dev/null @@ -1,33 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: | - New control protocol between the Elastic Agent and its subprocesses. - Enables per integration health reporting and simplifies new input development, among other things. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1701 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 \ No newline at end of file diff --git a/changelog/fragments/1672911993-v2-directory.yaml b/changelog/fragments/1672911993-v2-directory.yaml deleted file mode 100644 index 992c10bbcaa..00000000000 --- a/changelog/fragments/1672911993-v2-directory.yaml +++ /dev/null @@ -1,33 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: upgrade - -# Change summary; a 80ish characters long description of the change. -summary: | - Internal directory structure change: addition of the components directory - (and removal of the downloads directory) to contain binaries and their associated artifacts. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1701 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911994-v2-packaging.yaml b/changelog/fragments/1672911994-v2-packaging.yaml deleted file mode 100644 index 729107e3d6d..00000000000 --- a/changelog/fragments/1672911994-v2-packaging.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: upgrade - -# Change summary; a 80ish characters long description of the change. -summary: | - All binaries for every supported integration will be bundled in the Elastic Agent by default. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent-shipper/pull/126 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911995-v2-diagnostic.yaml b/changelog/fragments/1672911995-v2-diagnostic.yaml deleted file mode 100644 index d411ab81806..00000000000 --- a/changelog/fragments/1672911995-v2-diagnostic.yaml +++ /dev/null @@ -1,34 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: breaking-change - -# Change summary; a 80ish characters long description of the change. -summary: | - Diagnostic: --pprof argument has been removed, it's now always provided. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -description: | - The diagnostic command is gathering diagnostic information about the Elastic Agent and each - component/unit ran by the Elastic Agent. --pprof argument has been removed: it's now always provided. - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1140 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911997-v2-inspect.yaml b/changelog/fragments/1672911997-v2-inspect.yaml deleted file mode 100644 index 6ecaad07077..00000000000 --- a/changelog/fragments/1672911997-v2-inspect.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: feature - -# Change summary; a 80ish characters long description of the change. -summary: | - Add inspect components command to inspect the computed components/units model of the current configuration (elastic-agent inspect components). - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1701 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672911999-v2-health-status.yaml b/changelog/fragments/1672911999-v2-health-status.yaml deleted file mode 100644 index ab1d29d383d..00000000000 --- a/changelog/fragments/1672911999-v2-health-status.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: enhancement - -# Change summary; a 80ish characters long description of the change. -summary: | - Health Status: Elastic Agent now indicates detailed status information for each component/unit. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/fleet-server/pull/1747 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/100 diff --git a/changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml b/changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml deleted file mode 100644 index 99e9c2fb81a..00000000000 --- a/changelog/fragments/1672912001-fix-duplicate-entries-on-upgrade.yaml +++ /dev/null @@ -1,33 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: bug-fix - -# Change summary; a 80ish characters long description of the change. -summary: | - Correctly preserve the Filebeat registry and other persistent input state during upgrades. - Eliminates event duplication after Elastic agent upgrades. - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: agent - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -pr: https://github.com/elastic/elastic-agent/pull/1701 - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/836 diff --git a/changelog/fragments/1672912002-osquery-known-issue.yaml b/changelog/fragments/1672912002-osquery-known-issue.yaml deleted file mode 100644 index f02f48a299f..00000000000 --- a/changelog/fragments/1672912002-osquery-known-issue.yaml +++ /dev/null @@ -1,32 +0,0 @@ -# Kind can be one of: -# - breaking-change: a change to previously-documented behavior -# - deprecation: functionality that is being removed in a later release -# - bug-fix: fixes a problem in a previous version -# - enhancement: extends functionality but does not break or fix existing behavior -# - feature: new functionality -# - known-issue: problems that we are aware of in a given version -# - security: impacts on the security of a product or a user’s deployment. -# - upgrade: important information for someone upgrading from a prior version -# - other: does not fit into any of the other categories -kind: known-issue - -# Change summary; a 80ish characters long description of the change. -summary: | - OSQuery live query results can take up to 5 mins to show up in Kibana - -# Long description; in case the summary is not enough to describe the change -# this field accommodate a description without length limits. -# description: - -# Affected component; a word indicating the component this changeset affects. -component: osquery - -# PR URL; optional; the PR number that added the changeset. -# If not present is automatically filled by the tooling finding the PR where this changelog fragment has been added. -# NOTE: the tooling supports backports, so it's able to fill the original PR number instead of the backport PR number. -# Please provide it if you are adding a fragment for a different PR. -#pr: - -# Issue URL; optional; the GitHub issue related to this changeset (either closes or is part of). -# If not present is automatically filled by the tooling with the issue linked to the PR number. -issue: https://github.com/elastic/elastic-agent/issues/2066 From 7a42bf6ea78f7b88bd3fa4dcfc548f924c72d9ee Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 21:25:46 +0100 Subject: [PATCH 4/7] Removing non visible changes --- changelog/8.6.0.yaml | 49 +------------------------------------------- 1 file changed, 1 insertion(+), 48 deletions(-) diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml index 1ef8e83a75d..9ba614b69ac 100644 --- a/changelog/8.6.0.yaml +++ b/changelog/8.6.0.yaml @@ -20,7 +20,7 @@ entries: issue: - https://github.com/elastic/elastic-agent/issues/1069 timestamp: 1666095433 - file: + file:x name: 1666095433-service_runtime_v2.yaml checksum: 94f777454bf571caf8da848441c43eb6d7b3bc10 - kind: feature @@ -57,41 +57,6 @@ entries: file: name: 1668483030-common-expression-language.yaml checksum: 82427fc514372c067e140837177c8d81131ed424 - - kind: bug-fix - summary: V2 Provide Fleet configuration to APM server - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1745 - issue: - - https://github.com/elastic/elastic-agent/issues/1737 - timestamp: 1668645651 - file: - name: 1668645651-apm-fleet-config.yaml - checksum: ce8dc3cc4c598555ef05bfa0aa4f8daf0ac680b2 - - kind: bug-fix - summary: apm-monitoring - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1748 - issue: [] - timestamp: 1668679987 - file: - name: 1668679987-apm-monitoring.yaml - checksum: ef78089de487eeea3728f872de9d544bdecf1c5b - - kind: bug-fix - summary: Change config comparison to fix false unit update events - description: "" - component: runtime - pr: - - https://github.com/elastic/elastic-agent/pull/1766 - issue: - - https://github.com/elastic/elastic-agent/issues/1738 - timestamp: 1669066497 - file: - name: 1669066497-struct-compare-unit-update.yaml - checksum: 513333eb8795e990ef632df7e2b71120feeaf892 - kind: feature summary: Reimplement processes route description: Re-implement processes route to restore compatibility with the current cloud health checks @@ -128,18 +93,6 @@ entries: file: name: 1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml checksum: 80fb772957944cd3687aa999595d6be1b4d96d2a - - kind: bug-fix - summary: Fix erroneous http url directory created for monitoring - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1811 - issue: - - https://github.com/elastic/elastic-agent/issues/1806 - timestamp: 1669668741 - file: - name: 1669668741-fix-erroneous-http-url-directory-created-for-monitoring.yaml - checksum: d2c3b670e658413f5aa3bd650d79900dc7bc720a - kind: bug-fix summary: Fix osqueryd and osquery-extension.ext permissions description: "" From 45c8f28388603ab50ae2a5d8c1acc1ebc3e94c57 Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 21:28:10 +0100 Subject: [PATCH 5/7] Correcting typo --- changelog/8.6.0.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml index 9ba614b69ac..dae30119c54 100644 --- a/changelog/8.6.0.yaml +++ b/changelog/8.6.0.yaml @@ -20,7 +20,7 @@ entries: issue: - https://github.com/elastic/elastic-agent/issues/1069 timestamp: 1666095433 - file:x + file: name: 1666095433-service_runtime_v2.yaml checksum: 94f777454bf571caf8da848441c43eb6d7b3bc10 - kind: feature From 657be9f9240b2d2eb60260d18ceddd2e7744718e Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 21:39:47 +0100 Subject: [PATCH 6/7] New clean of non visible changes --- changelog/8.6.0.yaml | 75 ++------------------------------------------ 1 file changed, 2 insertions(+), 73 deletions(-) diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml index dae30119c54..8fb12928468 100644 --- a/changelog/8.6.0.yaml +++ b/changelog/8.6.0.yaml @@ -11,18 +11,6 @@ entries: file: name: 1665780486-heartbeat-es-output-only.yaml checksum: 361f993ba3220aef531f7949308e61d2cbf82e03 - - kind: feature - summary: Service runtime for V2 - description: Service runtime for V2, tailored specifically for Endpoint service. - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1529 - issue: - - https://github.com/elastic/elastic-agent/issues/1069 - timestamp: 1666095433 - file: - name: 1666095433-service_runtime_v2.yaml - checksum: 94f777454bf571caf8da848441c43eb6d7b3bc10 - kind: feature summary: Upgrade node to 18.12.0 description: "" @@ -58,19 +46,7 @@ entries: name: 1668483030-common-expression-language.yaml checksum: 82427fc514372c067e140837177c8d81131ed424 - kind: feature - summary: Reimplement processes route - description: Re-implement processes route to restore compatibility with the current cloud health checks - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1773 - issue: - - https://github.com/elastic/elastic-agent/issues/1731 - timestamp: 1669159455 - file: - name: 1669159455-reimplement-processes-route.yaml - checksum: cbeb5b5766bf733dd5e200a69353e326c642a971 - - kind: feature - summary: Capture stdout/stderr of all spawned components and adjust default log level to info for all components + summary: Capture stdout/stderr of all subprocesses and adjust default log level to info for all components. description: "" component: "" pr: @@ -81,53 +57,6 @@ entries: file: name: 1669236059-Capture-stdout-stderr-of-all-spawned-components-to-simplify-logging.yaml checksum: b4cf9cff0ef13bd168cadc80f89c4969b49fb378 - - kind: bug-fix - summary: Fix Elastic-Agent fails to re-start during upgrade - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1805 - issue: - - https://github.com/elastic/elastic-agent/issues/1788 - timestamp: 1669665017 - file: - name: 1669665017-fix-nil-action-ack-crash-after-local-upgrade.yaml - checksum: 80fb772957944cd3687aa999595d6be1b4d96d2a - - kind: bug-fix - summary: Fix osqueryd and osquery-extension.ext permissions - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1829 - issue: [] - timestamp: 1669739947 - file: - name: 1669739947-fix-osqueryd-and-osquery-extension.ext-permissions.yaml - checksum: cc8d9c7ab91b7e4c45a11b5b1347238d3e757453 - - kind: feature - summary: Add agent logging level to fleet configuration - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1856 - issue: - - https://github.com/elastic/elastic-agent/issues/1853 - timestamp: 1669845868 - file: - name: 1669845868-add-agent-logging-level-to-fleet-configuration.yaml - checksum: 33cbf01b52f8cf30971d84fadbba10163197fe61 - - kind: feature - summary: Ensure unique input ID when variable substition occurs from a dynamic provider - description: "" - component: "" - pr: - - https://github.com/elastic/elastic-agent/pull/1866 - issue: - - https://github.com/elastic/elastic-agent/issues/1751 - timestamp: 1669928791 - file: - name: 1669928791-Ensure-unique-input-ID-when-variable-substition-occurs-from-a-dynamic-provider.yaml - checksum: c057e4c3420b9549dc31c8e13e58ad3992a8eb49 - kind: bug-fix summary: Elastic-agent will use local port when running fleet-server description: The elastic-agent will now use the 8221 locally bound port when running fleet-server instead of the external port (8220). @@ -178,7 +107,7 @@ entries: file: name: 1671748292-input-ids-are-required.yaml checksum: 3ca6d7c10ce16c72c74b67b18916407ad09459fd - - kind: breaking-change + - kind: upgrade summary: "New control protocol between the Elastic Agent and its subprocesses. \nEnables per integration health reporting and simplifies new input development, among other things.\n" description: "" component: agent From d080afca224c8e808195ccc4d4a19b9798e89718 Mon Sep 17 00:00:00 2001 From: Pierre HILBERT Date: Mon, 9 Jan 2023 22:29:22 +0100 Subject: [PATCH 7/7] Workaround for upgrade kind --- changelog/8.6.0.yaml | 29 ++++++++++++++++------------- 1 file changed, 16 insertions(+), 13 deletions(-) diff --git a/changelog/8.6.0.yaml b/changelog/8.6.0.yaml index 8fb12928468..625d6601a4d 100644 --- a/changelog/8.6.0.yaml +++ b/changelog/8.6.0.yaml @@ -35,7 +35,7 @@ entries: name: 1667571017-Add-support-for-running-the-elastic-agent-shipper.yaml checksum: b2f5a0a8f9933c9ee624457116295aa674ef2a23 - kind: feature - summary: Add Common Expression Language input mapping to the Filebeat spec. + summary: Add support for the Common Expression Language (CEL) Filebeat input type. description: "" component: spec pr: @@ -46,7 +46,7 @@ entries: name: 1668483030-common-expression-language.yaml checksum: 82427fc514372c067e140837177c8d81131ed424 - kind: feature - summary: Capture stdout/stderr of all subprocesses and adjust default log level to info for all components. + summary: Collect logs from sub-processes via stdout and stderr and write them to a single, unified Elastic Agent log file. description: "" component: "" pr: @@ -107,9 +107,11 @@ entries: file: name: 1671748292-input-ids-are-required.yaml checksum: 3ca6d7c10ce16c72c74b67b18916407ad09459fd - - kind: upgrade - summary: "New control protocol between the Elastic Agent and its subprocesses. \nEnables per integration health reporting and simplifies new input development, among other things.\n" - description: "" + - kind: feature + summary: New control protocol between the Elastic Agent and its subprocesses. + description: | + New control protocol between the Elastic Agent and its subprocesses. + Enables per integration health reporting and simplifies new input development, among other things. component: agent pr: - https://github.com/elastic/elastic-agent/pull/1701 @@ -119,9 +121,9 @@ entries: file: name: 1672911992-v2-control-protocol.yaml checksum: 837bf1d3f02ab63b94b5fbe5853b8163aaeb6f31 - - kind: upgrade - summary: "Internal directory structure change: addition of the components directory \n(and removal of the downloads directory) to contain binaries and their associated artifacts.\n" - description: "" + - kind: feature + summary: Internal directory structure change + description: Addition of the components directory (and removal of the downloads directory) to contain binaries and their associated artifacts. component: agent pr: - https://github.com/elastic/elastic-agent/pull/1701 @@ -131,9 +133,8 @@ entries: file: name: 1672911993-v2-directory.yaml checksum: 6ab87446b15a94993186754952e08c00a72c13ba - - kind: upgrade - summary: | - All binaries for every supported integration will be bundled in the Elastic Agent by default. + - kind: feature + summary: All binaries for every supported integration will be bundled in the Elastic Agent by default. description: "" component: agent pr: @@ -186,8 +187,10 @@ entries: name: 1672911999-v2-health-status.yaml checksum: eeb54c42273e877893abda9f56a92c2d31c4fa46 - kind: bug-fix - summary: "Correctly preserve the Filebeat registry and other persistent input state during upgrades. \nEliminates event duplication after Elastic agent upgrades.\n" - description: "" + summary: Preserve persistent input state during upgrades. + description: | + Correctly preserve the Filebeat registry and other persistent input state during upgrades. + Eliminates event duplication after Elastic agent upgrades. component: agent pr: - https://github.com/elastic/elastic-agent/pull/1701