<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#40122
# Details
* Adds deprecation warnings to `fleetctl apply`
* Adds alias conflict errors (i.e. using both new and deprecated keys in
the same spec) to `fleetctl apply`
* Adds logic around all deprecated field warnings to check the topic
first
* Disables deprecation warnings by default for `fleet serve`, `fleetctl
gitops` and `fleetctl apply`
* Enables deprecation warnings for dogfood via env var
To turn on warnings:
* In `fleet serve`, use either
`--logging_enable_topics=deprecated-field-names` or the
`FLEET_LOGGING_ENABLE_TOPICS=deprecated-field-names` env var
* In `fleetctl gitops` / `fleetctl apply` use either
`--enable-log-topics=deprecated-field-names` or
`FLEET_ENABLE_LOG_TOPICS=deprecated-field-names`
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [X] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files)
for more information.
## Testing
- [X] Added/updated automated tests
- [X] QA'd all new/changed functionality manually
tested in `fleetctl apply`, `fleet serve` and `fleet gitops` that
warnings are suppressed by default and added when the appropriate env
var or CLI option is used
## Summary
Updates the `/fleet-gitops` marketing page
(`website/views/pages/fleet-gitops.ejs`) and its meta tags
(`website/config/routes.js`) to lead with **infrastructure as code**
rather than **GitOps** throughout headings, body copy, and meta tags —
using varied, natural phrasing instead of rigidly prefixing "Fleet"
every time.
Also adds a new **AI-accelerated IT** section with Kilocode screenshot
reference and three pitch points about AI-accelerated device management.
### Changes
- Page title tag: `Fleet GitOps` → `Infrastructure as code`
- Meta description updated to emphasize infra-as-code
- Hero `<h4>`: `Fleet GitOps` → `Infrastructure as code`
- Bottom CTA `<h4>`: `Fleet GitOps` → `Infrastructure as code for your
devices`
- Hero paragraph rewritten to lead with infra-as-code
- Features list item heading: `Get to know Fleet infrastructure as code`
→ `Manage your infrastructure as code`
- Section heading: `Get to know Fleet infrastructure as code` →
`Infrastructure as code for your devices`
- Body copy: `adopt Fleet infrastructure as code` → `adopt
infrastructure as code for device management`
- Image alt text, caption, and two-column feature body copy updated
- Workshop CTA heading: `GitOps workshop` → `Infrastructure as code
workshop`
- Challenges section rewritten to lead with infra-as-code; GitOps still
mentioned where it fits naturally
- Testimonial quote updated to reference infra-as-code
- **New**: AI-accelerated IT section with Kilocode screenshot and three
pitch points:
- Everyone can contribute, but an expert from IT stays the human in the
loop
- Without GitOps there is no way to do AI-accelerated device management
- Iterate more quickly by reducing friction and hand-offs with natural
language changes via tools like Kilocode
### What stays as GitOps
- Workshop href (`/gitops-workshop`) — URL unchanged
- One natural mention: "If DevOps or GitOps is already used by an
organization…"
- Workshop link anchor text in the challenges section body
Built for
[mikermcneil](https://fleetdm.slack.com/archives/D0AFASLRHNU/p1771879170001129)
by [Kilo for Slack](https://kilo.ai/features/slack-integration)
---------
Co-authored-by: kiloconnect[bot] <240665456+kiloconnect[bot]@users.noreply.github.com>
Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com>
Co-authored-by: Kilo Code <kilo@kilo.ai>
This pull request adds Windows support for GIMP version 3.0.8-2 to the
maintained apps. It introduces new install and uninstall scripts,
updates the app metadata, and provides integration details for Fleet's
package management.
New GIMP Windows app integration:
* App metadata: Added `gimp.json` in the `winget` inputs directory,
specifying package details, installer type, architecture, and default
categories.
* App listing: Updated `apps.json` to include the new GIMP Windows entry
with platform, slug, unique identifier, and description.
Installer and uninstaller scripts:
* Install script: Added `gimp_install.ps1` for silent, machine-scope
installation using Inno Setup installer flags.
* Uninstall script: Added `gimp_uninstall.ps1` for silent removal,
including logic to locate the correct uninstaller and handle edge cases.
Fleet integration and versioning:
* App version definition: Created `gimp/windows.json` output file,
detailing version, installer URL, install/uninstall script references,
SHA256, and Fleet query for existence.
<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#39558
---------
Co-authored-by: Rachael Shaw <r@rachael.wtf>
This absolutely slams GitHub rate limits, but one API request per page
of issues plus one API request per issue is the only sure way to get
this data, so it is what it is. May need to add a "pick up where you
left off" feature but this is at least a starting point.
Added a note that mcp_listening_tables may raise flags in EDR tools due
to unusual network activity.
---------
Co-authored-by: Eric <eashaw@sailsjs.com>
Moved team_id in Batch update configuration profiles endpoint example
from request body to the request url.
---------
Co-authored-by: Rachael Shaw <r@rachael.wtf>
<!-- Add the related story/sub-task/bug number, like Resolves#123, or
remove if NA -->
**Related issue:** Resolves#40054
# Checklist for submitter
- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
## Testing
- [x] Added/updated automated tests
- [x] QA'd all new/changed functionality manually
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
## Release Notes
* **Refactor**
* Updated logging infrastructure across background jobs and worker
services to use standardized structured logging, improving consistency
and log output formatting across the system.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Annotate many software, app_store_apps, and fleet_maintained_apps
entries in it-and-security/teams/workstations.yml with a `categories`
field (e.g., Security, Productivity, Utilities, Browsers, Developer
tools, Communication). This adds metadata to better organize the
self-service catalog and improve filtering/UX for workstation app
management.
This pull request makes a minor update to the configuration for
company-owned mobile devices. The change enables the `setup_experience`
option for the Okta Verify app in the
`it-and-security/teams/company-owned-mobile-devices.yml` file.
Brock Walters