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

🎸 Policy automations: run scripts offline #23237

Open
15 tasks
noahtalerman opened this issue Oct 25, 2024 · 2 comments
Open
15 tasks

🎸 Policy automations: run scripts offline #23237

noahtalerman opened this issue Oct 25, 2024 · 2 comments
Assignees
Labels
~air-guitar ~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver customer-numa #g-orchestration Orchestration product group :product Product Design department (shows up on 🦢 Drafting board) story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

Goal

User story
As a _________________________________________,
I want to _________________________________________
so that I can _________________________________________.

Objective

Customer promises + high priority requests

Original requests

Context

  • Product designer: _________________________

Changes

Product

  • UI changes: TODO
  • CLI (fleetctl) usage changes: TODO
  • YAML changes: TODO
  • REST API changes: TODO
  • Fleet's agent (fleetd) changes: TODO
  • Activity changes: TODO
  • Permissions changes: TODO
  • Changes to paid features or tiers: TODO
  • Other reference documentation changes: TODO
  • 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.
@noahtalerman noahtalerman added story A user story defining an entire feature :product Product Design department (shows up on 🦢 Drafting board) ~air-guitar labels Oct 25, 2024
@noahtalerman noahtalerman self-assigned this Oct 25, 2024
@noahtalerman noahtalerman added Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. ~feature fest Will be reviewed at next Feature Fest and removed Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. ~air-guitar labels Nov 14, 2024
@noahtalerman noahtalerman changed the title 🎸Auto-heal Wi-Fi while Macs are offline Auto-heal Wi-Fi while Macs are offline Nov 14, 2024
@noahtalerman noahtalerman added ~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver and removed ~feature fest Will be reviewed at next Feature Fest labels Nov 14, 2024
@noahtalerman noahtalerman added the #g-endpoint-ops Endpoint ops product group label Nov 22, 2024
@noahtalerman noahtalerman changed the title Auto-heal Wi-Fi while Macs are offline Policy automations: run scripts offline Dec 3, 2024
@noahtalerman
Copy link
Member Author

Hey @rachaelshaw heads up that I passed this user story to you. I need your help driving this one. I scheduled a call w/ you, me, and @sharon-fdm to better understand if we can use evented tables to make the policy failure => script run really fast.

@noahtalerman noahtalerman changed the title Policy automations: run scripts offline 🎸 Policy automations: run scripts offline Dec 11, 2024
@noahtalerman
Copy link
Member Author

TODO @noahtalerman: Add latest Gong snippet to the request

@noahtalerman noahtalerman added #g-orchestration Orchestration product group and removed #g-endpoint-ops Endpoint ops product group labels Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
~air-guitar ~customer promise A feature request from a Fleet customer that Fleet has contractually agreed to deliver customer-numa #g-orchestration Orchestration product group :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