Open ddribeiro opened 2 weeks ago
Hey @ddribeiro, great catch.
Even though it's not workflow blocking, can you please surface this during the next feature fest on 2024-09-12? A copy change here, would be a really quick-win improvement.
I think the "double-click" comes from a macOS bias. We automatically pop open the file explorer when we create a fleetd package on a macOS host.
Also, when you get the chance, can you please record a quick Loom of the experience when creating fleetd on Linux? (.deb) Do we open some file explorer? Does Linux have one?
That would be really helpful for everyone's learning/understanding.
TODO @noahtalerman: Track a higher level objective for this story and link this story and other small UX wins
Problem
Upon successful creation of a
fleet-osquery
installer,fleetctl
displays guidance for how to use the installer to add a device to Fleet.However, for
.deb
installers, the directions to double-click are incorrect. A Linux user would usedpkg -i
to install the .deb instead of double-clicking.Potential solutions
Update the messaging in
fleetctl
to direct the user to usedpkg -I
to add the host to Fleet.What is the expected workflow as a result of your proposal?
A Linux user would use `fleetctl` to create a `.deb` installer. Upon successful creation, they would be given directions to use `dpkg -i` to add the host to Fleet instead of double-clicking.