Changes:
- Changed the name of the `type` prop of the `<call-to-action>`
component to `preset`
- Updated `<call-to-action>` components in articles to use the new prop
name
- Updated the article formatting guide in the Handbook to document how
to use a `<call-to-action>` preset and added examples of our two
presets.
Added a note concerning the changes to osquery packs
# Checklist for submitter
If some of the following don't apply, delete the relevant line.
- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
- For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
Closes: #9786
Changes:
- Updated the <call-to-action> component to add support for a new prop:
`type`. This can be set to `premium-upgrade` or `mdm-beta`. If this prop
is provided, the component will render a call to action for the limited
MDM beta or Fleet Premium.
- Example usage: `<call-to-action type="mdm-beta"></call-to-action>`
- Added a CTA for upgrading to Fleet premium to the `Fleet 4.27.0`
release article
- Added a CTA for the MDM beta to the `Fleet 4.26.0` release article
