From 762055974d17784e22bd34d57a443923e54e1eac Mon Sep 17 00:00:00 2001 From: gillespi314 <73313222+gillespi314@users.noreply.github.com> Date: Tue, 29 Oct 2024 15:59:53 -0500 Subject: [PATCH 1/4] Update links in guide to puppet module --- articles/puppet-module.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/articles/puppet-module.md b/articles/puppet-module.md index 78dc4b0c7490..74fc7dc126fe 100644 --- a/articles/puppet-module.md +++ b/articles/puppet-module.md @@ -20,9 +20,9 @@ Install [Fleet's Puppet module](https://forge.puppet.com/modules/fleetdm/fleetdm ### Step 2: configure Puppet to talk to Fleet using Heira -1. In Fleet, create an API-only user with the GitOps role. Instructions for creating an API-only user are [here](./fleetctl-CLI.md#create-an-api-only-user). +1. In Fleet, create an API-only user with the GitOps role. Instructions for creating an API-only user are [here](https://fleetdm.com/guides/fleetctl#create-api-only-user). -2. Get the API token for your new API-only user. Learn how [here](./fleetctl-CLI.md#get-the-api-token-of-an-api-only-user). +2. Get the API token for your new API-only user. Learn how [here](https://fleetdm.com/docs/rest-api/rest-api#log-in). 3. Set `fleetdm::host` and `fleetdm::token` values to your Fleet server's URL and the API token respectively. Here's an example of the Hiera YAML: From 76e1862bf69be8ad299b8e0e599293f4344bc888 Mon Sep 17 00:00:00 2001 From: gillespi314 <73313222+gillespi314@users.noreply.github.com> Date: Tue, 29 Oct 2024 16:19:08 -0500 Subject: [PATCH 2/4] Update puppet module guide --- articles/puppet-module.md | 6 +++--- docs/REST API/rest-api.md | 5 +++-- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/articles/puppet-module.md b/articles/puppet-module.md index 74fc7dc126fe..bf08e6cc115b 100644 --- a/articles/puppet-module.md +++ b/articles/puppet-module.md @@ -99,11 +99,11 @@ Set the `ensure` parameter to `absent` to create teams that exclude specific pro For more examples check out the `examples/` folder in Fleet's GitHub repository [here](https://github.com/fleetdm/fleet/tree/main/ee/tools/puppet/fleetdm/examples). -> Note that all teams created by Puppet inherit the bootstrap package, macOS Setup Assistant settings, and end user authentication settings from "No team." Learn more about these [here](./mdm-setup.md). In addition all teams automatically enable disk encryption. Learn more about disk encryption [here](./MDM-disk-encryption.md). +> Note that all teams created by Puppet inherit the bootstrap package, macOS Setup Assistant settings, and end user authentication settings from "No team." Learn more about these [here](https://fleetdm.com/guides/macos-setup-experience). In addition all teams automatically enable disk encryption. Learn more about disk encryption [here](https://fleetdm.com/guides/enforce-disk-encryption). ## Release host -If you set `await_device_configured` to `true` in your [macOS Setup Assistant settings](./mdm-setup.md#macos-setup-assistant), you can use the `fleetdm::release_device` function to release the host from the Setup Assistant. +If you set `enable_release_device_manually` to `true` in your [macOS setup experience](https://fleetdm.com/docs/rest-api/rest-api#configure-setup-experience), you can use the `fleetdm::release_device` function to release the host from the Setup Assistant. Here's what your Puppet code, with error handling, will look like: @@ -149,7 +149,7 @@ if $err != '' { } ``` -The above example includes the XML payload for the `EnableRemoteDesktop` MDM command. Learn more about creating the payload for other custom commands [here](./MDM-commands.md). +The above example includes the XML payload for the `EnableRemoteDesktop` MDM command. Learn more about creating the payload for other custom commands [here](https://fleetdm.com/guides/mdm-commands). diff --git a/docs/REST API/rest-api.md b/docs/REST API/rest-api.md index efa44a27066d..3f10a7ae839c 100644 --- a/docs/REST API/rest-api.md +++ b/docs/REST API/rest-api.md @@ -6105,7 +6105,7 @@ The summary can optionally be filtered by team ID. } ``` -### Turn on end user authentication for macOS setup +### Configure setup experience _Available in Fleet Premium_ @@ -6128,7 +6128,8 @@ _Available in Fleet Premium_ ```json { "team_id": 1, - "enabled_end_user_authentication": true + "enable_end_user_authentication": true, + "enable_release_device_manually": true } ``` From 20c8bf1ae590634602f3caf64eb5115aca8101fb Mon Sep 17 00:00:00 2001 From: Mike Thomas <78363703+mike-j-thomas@users.noreply.github.com> Date: Wed, 30 Oct 2024 08:37:48 +0900 Subject: [PATCH 3/4] updated sub-nav for "Setup experience" Updated "Turn on end user authentication for macOS setup" in the sub-nav