Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Dec 2, 2025

Summary

Fixes #[Fleet]: Standalone Agent Upgrade Commands not displayed for Non-macOS

The standalone agent upgrade documentation only showed macOS commands. Added tabbed interface with upgrade commands for all supported platforms:

  • macOS: /Library/Elastic/Agent/
  • Linux: /opt/Elastic/Agent/
  • Windows: C:\Program Files\Elastic\Agent\ with PowerShell admin instructions
  • DEB/RPM: Direct command (binary in PATH via systemd install)

Uses same tab-set syntax as install-standalone-elastic-agent.md and paths from installation-layout.md.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

Tool(s) and model(s) used: GitHub Copilot (Claude)

Original prompt

This section details on the original issue you should resolve

<issue_title>[Fleet]: Standalone Agent Upgrade Commands not displayed for Non-macOS</issue_title>
<issue_description>Description:
Upgrade standalone agents section only displays macOS upgrade commands. Upgrade commands for other operating systems are missing.

Link:
https://www.elastic.co/docs/reference/fleet/upgrade-standalone

Screen-shot:

Image

Whats working fine

  • Installation commands are available for all operating systems.

Expected Result
Upgrade commands for standalone agents should be available for all supported operating systems/artifacts. </issue_description>

<agent_instructions>Here's the file: https://github.com/elastic/docs-content/edit/main/reference/fleet/upgrade-standalone.md

Add Linux, Windows, DEB, and RPM instructions. An example of the syntax is available here: https://www.elastic.co/docs/reference/fleet/install-standalone-elastic-agent (https://github.com/elastic/docs-content/edit/main/reference/fleet/install-standalone-elastic-agent.md).</agent_instructions>

Comments on the Issue (you are @copilot in this section)


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

Co-authored-by: bmorelli25 <5618806+bmorelli25@users.noreply.github.com>
Copilot AI changed the title [WIP] Add standalone agent upgrade commands for Linux and Windows Add Linux, Windows, DEB, and RPM standalone agent upgrade commands Dec 2, 2025
Copilot AI requested a review from bmorelli25 December 2, 2025 16:08
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

🔍 Preview links for changed docs

@bmorelli25 bmorelli25 marked this pull request as ready for review December 3, 2025 20:21
@bmorelli25 bmorelli25 requested a review from a team as a code owner December 3, 2025 20:21
@github-actions
Copy link

github-actions bot commented Dec 3, 2025

Vale Linting Results

Summary: 2 suggestions found

💡 Suggestions (2)
File Line Rule Message
reference/fleet/upgrade-standalone.md 46 Elastic.Acronyms 'DEB' has no definition.
reference/fleet/upgrade-standalone.md 54 Elastic.Acronyms 'RPM' has no definition.

From the PowerShell prompt, change to the directory where you installed {{agent}}, and run:

```shell
cd "C:\Program Files\Elastic\Agent"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn’t the sentence on L42 make this line redundant?

In fact, maybe L42 could be adapted and moved to precede the tabs to fit all cases? 🤔 Then we could keep only the elastic-agent command in the code blocks.

(I was also wondering whether in that case we could also merge the macOS/Linux tabs into a single tab and maybe the DEB/RPM tabs into another — or is it worth having a separate tab for each?)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(I was also wondering whether in that case we could also merge the macOS/Linux tabs into a single tab and maybe the DEB/RPM tabs into another — or is it worth having a separate tab for each?)

I was mostly matching the tabs on the parent page: https://www.elastic.co/docs/reference/fleet/install-standalone-elastic-agent. AFAIK, this is the pattern we follow on all (most?) pages. I think it makes sense to keep it this way.

Doesn’t the sentence on L42 make this line redundant?

Yes, good call!

To upgrade a standalone agent running on an edge node:

1. Make sure the `elastic-agent` service is running.
2. From the directory where {{agent}} is installed, run the `upgrade` command to upgrade to a new version. Not sure where the agent is installed? Refer to [Installation layout](/reference/fleet/installation-layout.md).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vishaangelova you're right that this step already tells folks to move to the right directory. I've simplified the instructions below. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Fleet]: Standalone Agent Upgrade Commands not displayed for Non-macOS

3 participants