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

Create policies automatically for custom packages #23344

Open
15 tasks
marko-lisica opened this issue Oct 29, 2024 · 0 comments
Open
15 tasks

Create policies automatically for custom packages #23344

marko-lisica opened this issue Oct 29, 2024 · 0 comments
Assignees
Labels
customer-preston :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@marko-lisica
Copy link
Member

marko-lisica commented Oct 29, 2024

Goal

User story
As an IT admin,
I want to add a custom package and have Fleet create policy automatically
so that I can deploy software to all my hosts w/o having to write a policy.

Objective

Context

Changes

Product

  • UI changes: Figma link
  • CLI (fleetctl) usage changes: No changes.
  • YAML changes: No changes.
  • REST API changes: No changes.
  • Fleet's agent (fleetd) changes: No changes.
  • Activity changes: No changes.
  • Permissions changes: Permissions changes: No permissions changes. Software add/edit/remove permissions are already specified in the permissions guide.
  • Changes to paid features or tiers: Available in Fleet Premium only
  • Other reference documentation changes: No changes.
  • Once shipped, requester has been notified

Engineering

  • Feature guide changes: TODO
  • Database schema migrations: TODO
  • Load testing: TODO

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

QA

Risk assessment

  • Requires load testing: TODO
  • Risk level: Low / High TODO
  • Risk description: TODO

Manual testing steps

  1. Step 1
  2. Step 2
  3. Step 3

Testing notes

Confirmation

  1. Engineer (@____): Added comment to user story confirming successful completion of QA.
  2. QA (@____): Added comment to user story confirming successful completion of QA.
@marko-lisica marko-lisica added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) labels Oct 29, 2024
@marko-lisica marko-lisica self-assigned this Oct 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-preston :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature
Development

No branches or pull requests

2 participants