Allen Houchins
7c73da5369
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Related to #47981 ## What this does (dogfood GitOps unblock — step 1 of 2) The GitOps run for the mobile-device fleets fails while applying app store apps: ``` applying app store apps for fleet: "📱🏢 Employee-issued mobile devices": Validation Failed: Error 1062 (23000): Duplicate entry '303-?️ Productivity' for key 'software_categories.idx_software_categories_team_id_name' ``` **Root cause:** the category names in the YAML are correct (plain `"Productivity"`, etc., which translate server-side to the canonical emoji names). The conflict is a **stale stored category row** for the team. The `software_categories.(team_id, name)` unique index uses `utf8mb4_unicode_ci`, which treats the Unicode variation selector `U+FE0F` as ignorable. An earlier build stored Productivity as `🖥 Productivity` (no selector); today's code produces the canonical `🖥️ Productivity` (with selector). Those are *equal* to the index but *distinct* to Go's `strings.EqualFold`, so the existence check misses the stale row and the insert collides. This only affects the two variation-selector categories — `🖥️ Productivity` and `🛠️ Utilities` — which is why the failure is on Productivity. **This PR (step 1):** temporarily removes the `categories:` blocks from `company-owned-mobile-devices.yml` and `personal-mobile-devices.yml`. With no categories to insert, the app store batch applies cleanly, and Fleet's `deleteUnusedSelfServiceCategories` cleanup then purges the stale rows for those teams. Apps still install; they're just uncategorized until step 2. **Step 2 (follow-up):** once this is applied, revert this PR to re-add the categories. The teams will have no stale rows by then, so the canonical categories get created fresh and the apps are categorized correctly. The permanent fix (makes the category insert idempotent so any stored byte form is tolerated) is tracked separately under #47981. > Note: `workstations.yml` uses the same categories and may need the same treatment if that fleet also has a stale row — not included here since only the mobile fleets are confirmed failing. # Checklist for submitter - [x] Changes file: N/A — dogfood GitOps config only, no product code or user-visible product change. - [x] Input data is properly validated: N/A — removing config, no new inputs. ## Testing - [x] Verified both files remain valid YAML and all 24 app store apps per fleet are preserved (only `categories:` blocks removed; comments/formatting intact). - [ ] Confirm a GitOps dry run passes before merge. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Chores** * Simplified app catalog entries for iOS and iPadOS devices by removing category metadata while preserving all app functionality and settings. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
News · Report a bug · Docs · Why open source? · Art
Open-source platform for IT and security teams with thousands of computers. Designed for APIs, GitOps, webhooks, YAML, and humans.
What's it for?
Fleet gives you a single system to secure and maintain all your computing devices over the air. You can do MDM, patch stuff, deploy software, and verify anything, all from one place, across every OS your organization uses.
Fleet works directly with data and events from the native operating system, down to the bare metal. Strong diagnostics let you investigate errors on end-user devices and collect accurate audit evidence in minutes.
Get started
You can try Fleet out for yourself, or grab time with one of the maintainers to chat.
Is it any good?
Fleet is used in production by IT and security teams managing thousands of devices. Many deployments support tens of thousands of hosts, and a few large organizations manage 400,000 or more.
Supported platforms
- Linux (all distros)
- macOS
- Windows
- Chromebooks
- iOS and Android (BYOD or corporate-owned)
- Amazon Web Services (AWS)
- Google Cloud (GCP)
- Azure (Microsoft cloud)
- Data centers
- Containers (kube, etc)
- Linux-based IoT devices
Infrastructure as code
Manage your fleet with GitOps, or use the GUI, REST API, webhook events, and the fleetctl command-line tool.
Linux support
First-class support for all major distros. Linux gets the same attention and visibility as macOS and Windows.
Visibility and compliance
Fleet can report on hundreds of attributes across your devices and ships with CIS benchmarks for macOS and Windows and comprehensive operating system, hardware, and software data. Check out the table reference documentation to see what's available.
Open by design
Fleet is open source and transparent about what it can and can't see. End users can verify exactly how the agent works and what data their company collects. Fleet collects only the data needed to manage and secure devices, not private activity like keystrokes, emails, or webcams.
Good neighbors
Ready-to-use, enterprise-friendly integrations exist for Snowflake, Splunk, GitHub Actions, Vanta, Elastic Jira, Zendesk, and more. Fleet also works with tools such as Munki, Chef, Puppet, Ansible, CrowdStrike, and SentinelOne.
Lighter than air
Fleet is lightweight and modular. You can use it for MDM without using it for security, and vice versa. You can turn off features you are not using.
Free as in free
The free version of Fleet will always be free. Fleet is independently backed and actively maintained with the help of many amazing contributors.
Longevity
The company behind Fleet is founded (and majority-owned) by true believers in open source. The company's business model is influenced by GitLab (NYSE: GTLB), with great investors, happy customers, and the capacity to become profitable at any time.
Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and our commitment to improving the product.
Chat
The Fleet community is full of kind and helpful people. Whether or not you are a paying customer, if you need help, just reach out.
Contributing 
Contributions are welcome, whether you answer questions on Slack / GitHub / LinkedIn, improve the documentation or website, write a tutorial, give a talk at a conference or local meetup, give an interview on a podcast, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
License
The free version of Fleet is available under the MIT license. The commercial license is also designed to allow contributions to paid features for users whose employment agreements allow them to contribute to open source projects. (See LICENSE.md for details.)
Fleet is built on osquery, nanoMDM, Nudge, and swiftDialog.