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

Custom packages: set minimum version and automatic install #22076

Open
14 tasks
noahtalerman opened this issue Sep 13, 2024 · 2 comments
Open
14 tasks

Custom packages: set minimum version and automatic install #22076

noahtalerman opened this issue Sep 13, 2024 · 2 comments
Labels
customer-preston story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

noahtalerman commented Sep 13, 2024

Goal

User story
As an IT admin,
I want to set a minimum version and automatically install custom package
so that I can deploy an app to all my workstations w/o having to write a policy.

Context

Higher-level objective: Auto-reinstall productivity apps when they’re out of date

Changes

Product

  • Reference documentation changes: Docs changes covered by API changes below.
  • UI changes: Figma link
  • CLI (fleetctl) usage changes: No fleetctl changes.
  • YAML changes: No YAML changes.
  • REST API changes: API design: Custom packages: set minimum version and automatic install #22477
  • Fleet's agent (fleetd) changes: No fleetd changes.
  • Activity changes: No activity changes.
  • Permissions changes: No permissions changes. Software add/edit/remove permissions are already specified in the permissions guide.
  • Changes to paid features or tiers: Available for Fleet Premium.

Engineering

  • Feature guide changes: TODO
  • Database schema migrations: TODO
  • Load testing: TODO

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

  • Requires load testing: TODO
  • Risk level: Low / High TODO
  • Risk description: TODO

Manual testing steps

  1. Step 1
  2. Step 2
  3. Step 3

Testing notes

Confirmation

  1. Engineer (@____): Added comment to user story confirming successful completion of QA.
  2. QA (@____): Added comment to user story confirming successful completion of QA.
@noahtalerman noahtalerman added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) labels Sep 13, 2024
@noahtalerman noahtalerman changed the title Automatically install Fleet-maintained app or custom package w/o having to write a policy Set minimum version and automatically install custom package Sep 20, 2024
@noahtalerman noahtalerman changed the title Set minimum version and automatically install custom package Custom package: Set minimum version and automatically install Sep 20, 2024
@noahtalerman noahtalerman changed the title Custom package: Set minimum version and automatically install Custom package: set minimum version and automatically install Sep 20, 2024
@noahtalerman noahtalerman changed the title Custom package: set minimum version and automatically install Custom package: set minimum version and automatic install Sep 20, 2024
@noahtalerman noahtalerman changed the title Custom package: set minimum version and automatic install Custom packages: set minimum version and automatic install Sep 20, 2024
rachaelshaw added a commit that referenced this issue Sep 27, 2024
#22477)

API design for: #22076

---------

Co-authored-by: Rachael Shaw <r@rachael.wtf>
@noahtalerman noahtalerman changed the title Custom packages: set minimum version and automatic install Custom packages: automatic install Sep 30, 2024
@noahtalerman noahtalerman changed the title Custom packages: automatic install Custom packages: set minimum version and automatic install Sep 30, 2024
@noahtalerman
Copy link
Member Author

noahtalerman commented Sep 30, 2024

Hey @marko-lisica I think let's set this user story aside. I think we're already at mission critical app management parity for custom packages.

But please keep the wireframes b/c we might come back to these workflows when we get feedback from customers who use the policy automations feature.

@noahtalerman
Copy link
Member Author

noahtalerman commented Sep 30, 2024

Hey @zayhanlon heads up that we set this user story aside and pulled it out of the current design sprint.

We realized that Fleet is already at mission critical app management parity for custom apps/packages.

Other MDM solutions ask the IT admin to write a custom policy (w/ a script instead of osquery query) to trigger custom app install.

Fleet already supports this workflow using the install software policy automation. Guide is here.

Triggering Fleet-maintained app installs w/o writing a custom policy is a mission critical app management workflow. There's a user story for that in the current design sprint here: #22077

@noahtalerman noahtalerman removed the :product Product Design department (shows up on 🦢 Drafting board) label Oct 2, 2024
marko-lisica added a commit that referenced this issue Oct 3, 2024
We deprioritized #22076 so I'm removing changes that are merged into docs branch.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-preston story A user story defining an entire feature
Development

No branches or pull requests

3 participants