Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support "No team" for policies #21790

Closed
jacobshandling opened this issue Sep 3, 2024 · 11 comments
Closed

Support "No team" for policies #21790

jacobshandling opened this issue Sep 3, 2024 · 11 comments
Assignees
Labels
customer-preston #g-endpoint-ops Endpoint ops product group P2 Prioritize as urgent :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Milestone

Comments

@jacobshandling
Copy link
Contributor

jacobshandling commented Sep 3, 2024

@noahtalerman: YAML files reference doc updates are here: #22307


Flows to include in QA (non-exhaustive):

  • On another page, switch to all teams –> go to Policies page, ensure No teams maintained
  • Start on Policies page, select No team, navigate to another no-team supported page (e.g. Hosts), navigate back, ensure No teams selection maintained
  • Select 'No team', then:
    • Create a new policy, ensure successful team assignment (0)
    • Create a new custom policy, ensure successful team assignment (0)
    • Edit existing No-teams policy, ensure success
    • Delete existing No-teams policy
    • Policy automation install software for a no-team policy. (Jacob did this during sprint demos, but since this is the main use case for this feature, worth checking again)
@jacobshandling jacobshandling added #g-endpoint-ops Endpoint ops product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. P2 Prioritize as urgent and removed Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. labels Sep 3, 2024
@jacobshandling jacobshandling added this to the 4.57.0-tentative milestone Sep 3, 2024
@jacobshandling
Copy link
Contributor Author

jacobshandling commented Sep 3, 2024

Breaking these subtasks out into their own story as they are not directly coupled with their original parent story #19551

@jacobshandling jacobshandling added the story A user story defining an entire feature label Sep 3, 2024
@lukeheath
Copy link
Member

@zayhanlon Just wanted to make sure you know that we are building support for "No teams" in policies to enable customer-preston to use for automated software install.

@sharon-fdm
Copy link
Collaborator

QA DRI - @getvictor

@getvictor
Copy link
Member

GitOps bugs found: #22185

@getvictor
Copy link
Member

QA complete

@noahtalerman
Copy link
Member

@noahtalerman: YAML files reference doc updates are here: #22273

Hey @lucasmrod thanks for opening this PR to update the YAML files reference docs!

When you get the chance, can you please check if there are any other reference docs (maybe API) that need to be updated? Thanks :)

noahtalerman added a commit that referenced this issue Sep 23, 2024
@lukeheath lukeheath added :product Product Design department (shows up on 🦢 Drafting board) and removed :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. labels Sep 24, 2024
@noahtalerman
Copy link
Member

Hey @lucasmrod now that 4.57 is shipped, when you get the chance, can you please open a PR against the fleetdm/fleet-gitops repo to add a template teams/no-team.yml file?

Also, can you please check if there are any other reference docs (maybe API) that need to be updated? Thanks :)

@lucasmrod
Copy link
Member

now that 4.57 is shipped, when you get the chance, can you please open a PR against the fleetdm/fleet-gitops repo to add a template teams/no-team.yml file?

Sounds good. Do we want to add sample software+policies yaml on fleet-gitops too?

@lucasmrod
Copy link
Member

@noahtalerman fleetdm/fleet-gitops#51

noahtalerman pushed a commit to fleetdm/fleet-gitops that referenced this issue Sep 25, 2024
@noahtalerman
Copy link
Member

Hey @zayhanlon, heads up, this user story was shipped in 4.57 :)

@fleet-release
Copy link
Contributor

"No team" policies shine,
Guiding through a cloud city,
Fleet's path now refined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-preston #g-endpoint-ops Endpoint ops product group P2 Prioritize as urgent :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Development

No branches or pull requests

7 participants