From 32109158d2ffe9fd4dc138e10a56413557ccae8a Mon Sep 17 00:00:00 2001 From: kaanyalti Date: Sun, 3 Nov 2024 23:03:35 +0300 Subject: [PATCH] fix(5595): added fragment --- ...nt-agent-installation-with-force-flag.yaml | 30 +++++++++++++++++++ 1 file changed, 30 insertions(+) create mode 100644 changelog/fragments/1730662136-fix-development-agent-installation-with-force-flag.yaml diff --git a/changelog/fragments/1730662136-fix-development-agent-installation-with-force-flag.yaml b/changelog/fragments/1730662136-fix-development-agent-installation-with-force-flag.yaml new file mode 100644 index 0000000000..ab055350e3 --- /dev/null +++ b/changelog/fragments/1730662136-fix-development-agent-installation-with-force-flag.yaml @@ -0,0 +1,30 @@ +# 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: Fixes how the force flag behaves when installing an agent in development mode. Using the force flag will correctly replace the development agent as opposed to the production agent. + +# Long description; in case the summary is not enough to describe the change +# this field accommodate a description without length limits. +# NOTE: This field will be rendered only for breaking-change and known-issue kinds at the moment. +description: Currently using the force flag while installing an agent in development mode disregards the development flag and replaces the production agent. With this fix, the command correctly replaces the development agent with a new one. + +# Affected component; usually one of "elastic-agent", "fleet-server", "filebeat", "metricbeat", "auditbeat", "all", etc. +component: elastic-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/5877 +# 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