Files

T

kitzy 087e67644d Fix misspelled bootstrap-package article filename (#48833 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** NA

# Checklist for submitter

- [x] QA'd all new/changed functionality manually

## Summary

- Renamed `articles/manage-boostrap-package-with-gitops.md` to
`articles/manage-bootstrap-package-with-gitops.md` to fix the "boostrap"
typo (article title/content were already spelled correctly).
- Added a 301 redirect in `website/config/routes.js` from the old
misspelled URL (`/guides/manage-boostrap-package-with-gitops`) to the
corrected URL (`/guides/manage-bootstrap-package-with-gitops`).
- Updated the two internal links that pointed at the misspelled URL, in
`articles/enroll-macbook-neo-at-scale-with-fleet-zero-touch.md` and
`handbook/marketing/marketing-assets.md`.

## Testing

- [x] QA'd all new/changed functionality manually — verified the
redirect rule matches the existing pattern used for other renamed
`/guides/*` pages in `website/config/routes.js`.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Added a redirect for a misspelled guides URL so visitors are sent to
the correct page automatically.
* Improved navigation reliability for the affected guide link without
changing any other routes.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-07-08 16:48:08 -04:00

2.1 KiB

Raw Blame History

Manage bootstrap packages with GitOps

Bootstrap packages let you install custom software during device enrollment. This guide shows you how to manage them through GitOps using Fleet's API.

Note: Each fleet needs its own bootstrap package. Fleets can't share bootstrap packages.

Prerequisites

Before you start, you'll need:

A Fleet GitOps setup with an API-only user account
Access to Fleet's API endpoints
A bootstrap package ready to upload

Upload the bootstrap package

First, upload your bootstrap package to each fleet that needs it.

You can use either:

The Fleet UI to upload the package manually
The Create bootstrap package API endpoint to upload programmatically

Repeat this step for every fleet that needs the package.

Get the bootstrap package token

After uploading, retrieve the unique token for each fleet's bootstrap package.

Use the Get bootstrap package metadata API endpoint. The response includes the token you'll need for the next step.

Configure your GitOps fleet file

In each fleet's YAML configuration file, add the bootstrap_package field with the download URL:

bootstrap_package: "https://your-fleet-instance.com/api/v1/fleet/bootstrap?token=your-token-here"

Replace your-fleet-instance.com with your Fleet instance domain and your-token-here with the token from the previous step.

More information

Learn more about bootstrap packages and setup experiences in the setup experience guide.

2.1 KiB Raw Blame History