Skip to content
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

Automatically install software - Documentation #21056

Closed
sharon-fdm opened this issue Aug 5, 2024 · 3 comments
Closed

Automatically install software - Documentation #21056

sharon-fdm opened this issue Aug 5, 2024 · 3 comments
Assignees
Labels
#g-endpoint-ops Endpoint ops product group P2 Prioritize as urgent :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Milestone

Comments

@sharon-fdm
Copy link
Collaborator

sharon-fdm commented Aug 5, 2024

Clarify that adding software in Fleet makes it "available for install." And explain the two ways to install:
- manually install for an individual host
- go to Host details page and click "install"
- or self-service via "My device" page
- install automatically
- go to Policies page and have a policy failure trigger it

"How to use":

  1. Add package to your software that's available for install
  2. Manually install it on your test host
  3. Get ready to install automatically: write a policy query to check for the minimum version. If the host doesn't have that version
  • SOFTWARE_NAME and SOFTWARE_VERSION comes from the data in host vitals (step 2)
  1. Add package to the policy under Manage automations
  • Any existing policy pass/fail counts are cleared to reset the software install trigger

Here are the templates:

deb:
	SELECT 1 FROM deb_packages WHERE name = '<SOFTWARE_NAME>' AND version_compare(version, '<SOFTWARE_VERSION>') >= 0;

pkg:
	SELECT 1 FROM apps WHERE name = '<SOFTWARE_NAME>' AND version_compare(bundle_short_version, '<SOFTWARE_VERSION>') >= 0;

msi/exe:
	SELECT 1 FROM programs WHERE name = '<SOFTWARE_NAME>' AND version_compare(version, '<SOFTWARE_VERSION>') >= 0;
@sharon-fdm sharon-fdm added #g-endpoint-ops Endpoint ops product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.) labels Aug 5, 2024
@sharon-fdm sharon-fdm self-assigned this Aug 5, 2024
@sharon-fdm sharon-fdm added the P2 Prioritize as urgent label Aug 5, 2024
@lucasmrod
Copy link
Member

This issue seems to be a duplicate of #21842.

Noah recently edited #21842 to explain how users would use the feature (at a high level).

@lucasmrod
Copy link
Member

I've moved the description from #21842 to this issue which had a blank description.

@fleet-release
Copy link
Contributor

Software installs smooth,
Like clouds in glass city float,
Ease for users, true growth.

lukeheath added a commit that referenced this issue Sep 24, 2024
#21056

Document for policy-based automatic software installation.
See result
[here](https://github.com/fleetdm/fleet/blob/21056_auto_instal_document/articles/automatic-software-install-in-fleet.md#add-policy)

---------

Co-authored-by: spokanemac <jack@jdstrong.com>
Co-authored-by: Noah Talerman <noahtal@umich.edu>
Co-authored-by: JD <spokanemac@users.noreply.github.com>
Co-authored-by: Luke Heath <luke@fleetdm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#g-endpoint-ops Endpoint ops product group P2 Prioritize as urgent :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Development

No branches or pull requests

4 participants