-
Notifications
You must be signed in to change notification settings - Fork 190
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
Changed step 3 in the "Deploy a new agent" section. #5416
Conversation
… to agent in the deploy new agent section
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.
285ed79
|
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.
LGTM ✔️
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.16 4.4-7.16
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.16
# Create a new branch
git switch --create backport-5416-to-4.4-7.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b573bdc747ab323222e11561b1f4e29e2ad73753
# Push it to GitHub
git push --set-upstream origin backport-5416-to-4.4-7.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.16 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-4.4-7.10 4.4-7.10
# Navigate to the new working tree
cd .worktrees/backport-4.4-7.10
# Create a new branch
git switch --create backport-5416-to-4.4-7.10
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 b573bdc747ab323222e11561b1f4e29e2ad73753
# Push it to GitHub
git push --set-upstream origin backport-5416-to-4.4-7.10
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-4.4-7.10 Then, create a pull request where the |
* Changes in title and description of step assignment of name and group to agent in the deploy new agent section * Update changelog * Update changelog * Update changelog * Update changelog * Update changelog * Update CHANGELOG.md * sentences were changed and added in step 3 of the deploy new agent section * changelog * changelog * Changed the description of step 3 of the deploy a new agent section. --------- Co-authored-by: Álex Ruiz <[email protected]> (cherry picked from commit b573bdc)
* Changes in title and description of step assignment of name and group to agent in the deploy new agent section * Update changelog * Update changelog * Update changelog * Update changelog * Update changelog * Update CHANGELOG.md * sentences were changed and added in step 3 of the deploy new agent section * changelog * changelog * Changed the description of step 3 of the deploy a new agent section. --------- Co-authored-by: Álex Ruiz <[email protected]> (cherry picked from commit b573bdc)
* Changes in title and description of step assignment of name and group to agent in the deploy new agent section * Update changelog * Update changelog * Update changelog * Update changelog * Update changelog * Update CHANGELOG.md * sentences were changed and added in step 3 of the deploy new agent section * changelog * changelog * Changed the description of step 3 of the deploy a new agent section. --------- Co-authored-by: Álex Ruiz <[email protected]> (cherry picked from commit b573bdc)
} | ||
|
||
systemSelectorWazuhControlMacos() { | ||
if (this.state.selectedVersion == 'sierra') { | ||
return 'sudo /Library/Ossec/bin/wazuh-control start'; | ||
} else return ''; | ||
return '/Library/Ossec/bin/wazuh-control start'; |
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.
nitpick: This command needs to be run with sudo
. We should create another pull request or add the commit to fix this in the development branch 4.4 because this pull request was merged with the problem.
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.
Good catch
…n. (#5513) * Changed step 3 in the "Deploy a new agent" section. (#5416) * Changes in title and description of step assignment of name and group to agent in the deploy new agent section * Update changelog * Update changelog * Update changelog * Update changelog * Update changelog * Update CHANGELOG.md * sentences were changed and added in step 3 of the deploy new agent section * changelog * changelog * Changed the description of step 3 of the deploy a new agent section. --------- Co-authored-by: Álex Ruiz <[email protected]> (cherry picked from commit b573bdc) * Update with sudo register-agent.js
…n. (#5512) * Changed step 3 in the "Deploy a new agent" section. (#5416) * Changes in title and description of step assignment of name and group to agent in the deploy new agent section * Update changelog * Update changelog * Update changelog * Update changelog * Update changelog * Update CHANGELOG.md * sentences were changed and added in step 3 of the deploy new agent section * changelog * changelog * Changed the description of step 3 of the deploy a new agent section. --------- Co-authored-by: Álex Ruiz <[email protected]> (cherry picked from commit b573bdc) * Update with sudo register-agent.js
Description
Changed the title of step 3 of the deploy a new agent section:
"Optionally, assign a name and a group to the agent"
By:
"Optional settings"
Added a title to the agent name input of the deploy a new agent section:
"Assign an agent name"
Changed the description of step 3 of the deploy a new agent section:
"The agent name is set as the name of the host where it is deployed. You can set your own name in the field below. Note that the agent name cannot be changed once registered."
By:
"The deployment sets the endpoint hostname as the agent name by default. Optionally, you can set the agent name below."
Changed the placeholder of the agent name input of the deploy a new agent section:
"Name agent"
To:
"Agent name"
Added callout below the agent name entry of the deploy a new agent section:
Issues Resolved
#5415
Evidence
Test
Verify that these changes appear:
Changed the title of step 3 of the deploy a new agent section:
"Optionally, assign a name and a group to the agent"
By:
"Optional settings"
Added a title to the agent name input of the deploy a new agent section:
"Assign an agent name"
Changed the description of step 3 of the deploy a new agent section:
"The agent name is set as the name of the host where it is deployed. You can set your own name in the field below. Note that the agent name cannot be changed once registered."
By:
"The deployment sets the endpoint hostname as the agent name by default. Optionally, you can set the agent name below."
Changed the placeholder of the agent name input of the deploy a new agent section:
"Name agent"
To:
"Agent name"
Added callout below the agent name entry of the deploy a new agent section:
Check List
yarn test:jest