Support Fleet-hosted macOS setup bootstrap packages in GitOps

[kitzy]

Gong snippet: TODO

Problem

I want to configure macOS setup using GitOps and have Fleet host the bootstrap package, just like I can in the UI. Right now, GitOps requires me to use external storage for the bootstrap package, which adds complexity and another service to maintain.

What have you tried?

I've configured macos_setup in my GitOps YAML, but there's no option to reference a bootstrap package hosted by Fleet. The UI lets me upload a package directly to Fleet, but I can't replicate this workflow in GitOps. I'd need to set up and maintain a separate storage solution (like S3 or similar) just to serve the bootstrap package.

Potential solutions

Add a way to upload bootstrap packages to Fleet and reference them in GitOps configuration. This could work similarly to how other assets are managed—upload the package to Fleet (via API or fleetctl), then reference it by name or hash in the macos_setup YAML.

For example:

macos_setup:
  bootstrap_package: "https://my.fleet.server/bootstrap-pkg-v1.2.pkg"
  # or
  hash_sha256: 93782402d683ca5dc747c8a742bcdc4956bc2aedb200c2a5c24bceff8651e96b

What is the expected workflow as a result of your proposal?

1. Upload bootstrap package to Fleet server (via fleetctl or API)
2. Reference the uploaded package in GitOps YAML by name or ID
3. Fleet serves the bootstrap package to enrolling devices during setup
4. Update the package by uploading a new version and updating the YAML reference
5. No need to maintain separate storage infrastructure