feat: update fleetctl output to reference fleetd (#16612)

> Related issue: #16382

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [x] Manual QA for all new/changed functionality
This commit is contained in:
Jahziel Villasana-Espinoza
2024-02-06 09:30:00 -05:00
committed by GitHub
parent f076769ee2
commit e1dbbda706
2 changed files with 5 additions and 4 deletions
+1
View File
@@ -0,0 +1 @@
- Updates the copy in `fleetctl`'s output to reference `fleetd`.
+4 -4
View File
@@ -352,7 +352,7 @@ func packageCommand() *cli.Command {
zlog.Logger = zerolog.Nop()
}
fmt.Println("Generating your osquery installer...")
fmt.Println("Generating your fleetd agent...")
path, err := buildFunc(opt)
if err != nil {
return err
@@ -360,11 +360,11 @@ func packageCommand() *cli.Command {
path, _ = filepath.Abs(path)
fmt.Printf(`
Success! You generated an osquery installer at %s
Success! You generated fleetd at %s
To add this device to Fleet, double-click to open your installer.
To add this device to Fleet, double-click to install fleetd.
To add other devices to Fleet, distribute this installer using Chef, Ansible, Jamf, or Puppet. Learn how: https://fleetdm.com/docs/using-fleet/adding-hosts
To add other devices to Fleet, distribute fleetd using Chef, Ansible, Jamf, or Puppet. Learn how: https://fleetdm.com/learn-more-about/enrolling-hosts
`, path)
if !disableOpenFolder {
open.Start(filepath.Dir(path)) //nolint:errcheck