-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Agent] Rename agent to elastic-agent #17391
Conversation
Pinging @elastic/ingest-management (Project:fleet) |
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.
Small details in the YAML files we should use the right capitalization "Elastic Agent" without the dash.
@@ -1,5 +1,5 @@ | |||
###################### Agent Configuration Example ######################### | |||
|
|||
# This file is an example configuration file highlighting only the most common | |||
# options. The agent.reference.yml file from the same directory contains all the | |||
# options. The elastic-agent.reference.yml file from the same directory contains all the | |||
# supported options with more comments. You can use it as a reference. |
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.
In the YAML of documentation we should use the right capitalization to represent the product: "Elastic Agent"
@michalpristas I've tested locally, build the packages and play with it seems to be fine. I just saw with the latest changes in the CI we do not test the agent with Jenkins anymore. I am going to track that. |
[Agent] Rename agent to elastic-agent (elastic#17391) (cherry picked from commit 66609a3)
) * [Agent] Rename agent to elastic-agent (#17391) [Agent] Rename agent to elastic-agent (#17391) (cherry picked from commit 66609a3) * Add Elastic Agent in the Jenkinsfile (#17445) * Add Elastic Agent in the Jenkinsfile With the recent moves to Jenkins pipeline the Elastic Agent project was not currently tested. * Add Elastic Agent in the Jenkinsfile (#17445) * Add Elastic Agent in the Jenkinsfile With the recent moves to Jenkins pipeline the Elastic Agent project was not currently tested. * [Agent] Fix merge of config (#17399) [Agent] Fix merge of config #17399 * [Agent] Handle abs paths on windows correctly (#17461) * handle windows correctly * Missing commits from the initial merges of the agent -> master Co-authored-by: Michal Pristas <[email protected]> Co-authored-by: Pier-Hugues Pellerin <[email protected]>
What does this PR do?
This PR renames agent to elastic-agent.
packaging tested.
configuration variables such as
agent.id
are kept the same without a name change.Why is it important?
To provide less generic name for executable
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Fixes #17239