YAML files reference docs: windows_migration_enabled

[noahtalerman]

• Add missing reference docs for the following user story:
  • Option to automatically migrate Windows workstations #22075

[noahtalerman]

FYI @allenhouchins the new setting, windows_migration_enabled, does live under controls top-level key. We specify in the docs that it's default.yml only. Same for windows_enabled_and_configured and macos_migration (see below)

@lucasmrod do all 3 of these settings also work when you put them under /no-team.yml? Today, in dogfood today we have windows_enabled_and_configured set in /no-team.yml and not in default.yml.

[lucasmrod]

Do you mean these ones?

fleet/it-and-security/teams/no-team.yml

Lines 5 to 8 in 9d9fc9b

	macos_migration:
	enable: true
	mode: voluntary
	webhook_url: $DOGFOOD_MACOS_MIGRATION_WEBHOOK_URL

Basically whatever is under controls: can be put in no-team.yml (provided you are defining controls: in only one of the two no-team.yml or default.yml)

[lucasmrod]

But if windows_migration_enabled is a global setting maybe it should not be under controls?

[noahtalerman]

(provided you are defining controls: in only one of the two no-team.yml or default.yml)

@lucasmrod do we return an easy to understand error message if you have controls in no-team.yml and default.yml?

if windows_migration_enabled is a global setting maybe it should not be under controls?

Agreed. Probably should be under org_settings in default.yml. Customers who want to use controls (ex. configuration profiles) on "No team" team will have a weird experience. I tracked this as a feature request here so we don't lose it: #24938

[lucasmrod]

do we return an easy to understand error message if you have controls in no-team.yml and default.yml?

We fail fleetctl gitops with the following error: 'controls' cannot be set on both global config and on no-team.yml.