Skip to content

YAML files: Move global settings from controls to org_settings  #24938

@noahtalerman

Description

@noahtalerman
  • @noahtalerman: Problem is described in this PR and comment in GitHub: YAML files reference docs: windows_migration_enabled #24891 (comment)
  • @noahtalerman: In the interim you can only specify controls in either teams/no-team.yml or default.yml but not both. This means that if you want to run policies on hosts in "No team" and set global settings, your global settings have to live under teams/no-team.yml. This is confusing because those settings are global. They apply to all hosts.
  • @marko-lisica: Another problem is for items that are supported at the global level (not team level), do we want to error? And vice versa.

Metadata

Metadata

Assignees

No one assigned

    Labels

    ~dogfoodIssue resulted from Fleet's product dogfooding.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions