Remove references to "team" and "teams" #52795

Goal

FLEET_JIT_USER_ROLE_TEAM_ will be handled with #53925.

Changes

Product

• UI changes: Remove teams from frontend and the command palette #56349
• CLI (fleetctl) usage changes: Remove teams from fleetctl #56630
  • Removed commands, flags, and environment variables fail with:
    • The "fleetctl get teams" command is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
    • The "--team" flag is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
    • The "--policies-team" flag is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
    • The "--delete-other-teams" flag is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
    • The "DELETE_OTHER_TEAMS" environment variable is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
    • The "--fleet no-team" value is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
• YAML changes: Remove teams from the YAML docs #56209
  • Old GitOps keys are rejected, not ignored. For example, team_settings fails with The "team_settings" key is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
• REST API changes: Remove teams from the API docs #56092 Use "fleet" field names in the frontend #56415 Let the API accept fleet names for sorting and targets #56620 Remove teams URL paths from the API #56641 Make the frontend send and read the "fleet" names #56646 Keep the team ID out of script results #56679 Remove teams from the API #56680
  • Old paths return a 410 instead of a 404. For example, GET /api/v1/fleet/teams returns The "GET /teams" endpoint is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
  • Old parameters, response fields, sort keys, and the team target type are rejected with a 422, not silently ignored. For example, team_id returns The "team_id" parameter is not available anymore. What to use instead: https://fleetdm.com/learn-more-about/fleet-5-upgrade
• Fleet's agent (fleetd) changes: No changes
• Fleet server configuration changes: Remove teams from Fleet server configuration docs #56211
• Exposed, public API endpoint changes: No changes
  • Maybe in server/service/handler_deprecated_paths.go?
• fleetdm.com changes: No changes
• GitOps mode UI changes: No changes
• GitOps generation changes: See Remove teams from fleetctl #56630
• Activity changes: Remove teams from audit logs #56222
  • Engineering: We'll need a migration for the new activity names.
• Permissions changes: No changes
• Changes to paid features or tiers: No changes
• My device and fleetdm.com/better changes: No changes
• Usage statistics: No changes
• Compatibility: Breaking changes, but part of a major release.
• Other reference documentation changes: Remove teams from reference docs #56215
• First draft of test plan added
• Once shipped, requester has been notified
• Once shipped, dogfooding issue has been filed

Engineering

• Test plan is finalized
• Contributor API changes: Yes, see links above
• Feature guide changes: Yes, see links above
• Database schema migrations: Yes, activities

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

Risk assessment

• Risk level: High
• Risk description: Large surface area

Test plan

Make sure to go through the list and consider all events that might be related to this story, so we catch edge cases earlier.

Core flow

• Confirm there are no references to team/teams remaining.
• Confirm old team/teams endpoints return a 410, old parameters return a 422, and old GitOps keys and fleetctl commands, flags, and environment variables fail, each with its message and the migration guide link.

Edge cases

• TODO

Supplemental testing

Testing notes

Confirmation

1. Engineer: Added comment to user story confirming successful completion of test plan (include any special setup, test data, or configuration used during development/testing if applicable).
2. QA: Added comment to user story confirming successful completion of test plan.
3. QA: Determined whether this story needs Playwright automation.
   • Needs automation: Yes / No
   • If yes, filed a follow-up issue in the :help-qa project with status "Needs automation":