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.

Sign up for GitHub

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

Jump to bottom

VPP Auto-install: BE #26190

Open
iansltx opened this issue Feb 7, 2025 · 2 comments
Open

VPP Auto-install: BE #26190

iansltx opened this issue Feb 7, 2025 · 2 comments
Assignees
@iansltx
Labels
~backend Backend-related issue. #g-software Software product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)

Comments

@iansltx
Copy link
Member

iansltx commented Feb 7, 2025

No description provided.

@iansltx iansltx added the :product Product Design department (shows up on 🦢 Drafting board) label Feb 7, 2025
@iansltx
Copy link
Member Author

iansltx commented Feb 7, 2025

Hey team! Please add your planning poker estimate with Zenhub @jahzielv @ksykulev

@mostlikelee mostlikelee added ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.) #g-software Software product group ~backend Backend-related issue. :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. and removed :product Product Design department (shows up on 🦢 Drafting board) labels Feb 7, 2025
@mostlikelee
Copy link
Contributor

increased estimate for FMA and VPP autoinstall

iansltx added a commit that referenced this issue Feb 18, 2025
@iansltx
Add automatic policy creation for VPP apps
93be6cc 
For #26190. Also refactors automatic policy generation so we're reusing a bit of the custom package logic, and can reuse further when doing the same thing for FMA.

TODO:

* Tests on new code surface
* Potentially pull auto-install into VPPAppsTeams payload to minimize test diff
* Add same ability to FMA
* Add created_at/updated_at to VPP apps teams + migration backfill
@iansltx iansltx mentioned this issue Feb 18, 2025
Merged
5 tasks
iansltx added a commit that referenced this issue Feb 22, 2025
@iansltx
Allow automatic creation of software install policy for VPP and FMA a…
ce36352 
…pps in API (#26440)

For #26190. FMA is included here because the previous implementation was
client-side. QA'd manually. Follow-up PR soon with automated test coverage.

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

<!-- Note that API documentation changes are now addressed by the
product design team. -->

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.
See [Changes
files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files)
for more information.
- [x] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added/updated automated tests
- [x] A detailed QA plan exists on the associated ticket (if it isn't
there, work with the product group's QA engineer to add it)
- [x] Manual QA for all new/changed functionality
iansltx added a commit that referenced this issue Feb 24, 2025
@iansltx
Add automated test coverage for VPP, FMA auto-install
3133068 
For #26190.
@iansltx iansltx mentioned this issue Feb 24, 2025
Merged
1 task
iansltx added a commit that referenced this issue Feb 24, 2025
@iansltx
Add automated test coverage for VPP, FMA auto-install (#26571)
4abbb5e 
For #26190. Code is already merged, and tests didn't find any issues.

# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [x] Added/updated automated tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@iansltx iansltx

Labels
~backend Backend-related issue. #g-software Software product group :release Ready to write code. Scheduled in a release. See "Making changes" in handbook. ~sub-task A technical sub-task that is part of a story. (Not QA'd. Not estimated.)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iansltx @mostlikelee