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

Prevent auto-created policies for RPM/deb packages from running on Debian/RPM based Linux distributions #25007

Open
16 tasks
noahtalerman opened this issue Dec 24, 2024 · 1 comment
Labels
story A user story defining an entire feature

Comments

@noahtalerman
Copy link
Member

  • @noahtalerman: In Fleet 4.62, Fleet will auto-create policies to auto-install RPM/deb packages (user story here). In this iteration, policies for RPM packages will run on Debian Linux distributions and vice versa. RPM packages won't be installed on Debian Linux distros because the policy is written to always pass on Debian. More info in a dev note here.
  • In Fleet 4.62, Fleet will add the ability target software using labels (user story here).
  • The plan is to piggy-back on these stories and auto-apply the RPM label to RPM packages. This way, the policies for RPM distros won't run at all on Debian distros and vice versa.

Goal

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

Key result

Deliver customer promises

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
  • Once shipped, dogfooding issue has been filed

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 the story A user story defining an entire feature label Dec 24, 2024
@noahtalerman noahtalerman added Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. and removed Epic DO NOT USE. Auto-created by ZenHub, cannot be disabled. labels Dec 24, 2024
@noahtalerman
Copy link
Member Author

  • @noahtalerman: In Fleet 4.62, Fleet will auto-create policies to auto-install RPM/deb packages (user story here). In this iteration, policies for RPM packages will run on Debian Linux distributions and vice versa. RPM packages won't be installed on Debian Linux distros because the policy is written to always pass on Debian. More info in a dev note here.
  • In Fleet 4.62, Fleet will add the ability target software using labels (user story here).
  • The plan is to piggy-back on these stories and auto-apply the RPM label to RPM packages. This way, the policies for RPM distros won't run at all on Debian distros and vice versa.

FYI @eugkuo I filed this user story and added it to the "Automatically install and scope software within a team" request: #21825

It's mostly a cleanup ticket with small changes. I think we want to pick it up next sprint. I added it to the roadmap under the "Automatically install any software without writing custom policies" key result (KR).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
story A user story defining an entire feature
Development

No branches or pull requests

1 participant