-
Notifications
You must be signed in to change notification settings - Fork 185
Add Linux, Windows, DEB, and RPM standalone agent upgrade commands #4187
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: bmorelli25 <5618806+bmorelli25@users.noreply.github.com>
🔍 Preview links for changed docs |
| From the PowerShell prompt, change to the directory where you installed {{agent}}, and run: | ||
|
|
||
| ```shell | ||
| cd "C:\Program Files\Elastic\Agent" |
There was a problem hiding this comment.
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?)
There was a problem hiding this comment.
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!
Removed unnecessary 'cd' commands for upgrade instructions.
| 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). |
There was a problem hiding this comment.
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!
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:
/Library/Elastic/Agent//opt/Elastic/Agent/C:\Program Files\Elastic\Agent\with PowerShell admin instructionsUses same tab-set syntax as
install-standalone-elastic-agent.mdand paths frominstallation-layout.md.Generative AI disclosure
Tool(s) and model(s) used: GitHub Copilot (Claude)
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.