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

Add experimental software title name update endpoint for titles with a bundle ID #26938

Merged
merged 3 commits into from
Mar 7, 2025

Conversation

iansltx
Copy link
Member

@iansltx iansltx commented Mar 7, 2025

For #26933.

Checklist for submitter

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

  • Changes file added for user-visible changes in changes/, orbit/changes/ or ee/fleetd-chrome/changes.
    See Changes files for more information.
  • Input data is properly validated, SELECT * is avoided, SQL injection is prevented (using placeholders for values in statements)
  • Added/updated automated tests
  • 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)
  • Manual QA for all new/changed functionality

Copy link

codecov bot commented Mar 7, 2025

Codecov Report

Attention: Patch coverage is 65.62500% with 11 lines in your changes missing coverage. Please review.

Project coverage is 64.01%. Comparing base (a0f8d09) to head (c4506d8).
Report is 8 commits behind head on main.

Files with missing lines Patch % Lines
server/service/software_titles.go 69.23% 7 Missing and 1 partial ⚠️
server/datastore/mysql/software_titles.go 40.00% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #26938      +/-   ##
==========================================
- Coverage   64.02%   64.01%   -0.01%     
==========================================
  Files        1701     1701              
  Lines      162252   162279      +27     
  Branches     4272     4272              
==========================================
+ Hits       103874   103889      +15     
- Misses      50319    50329      +10     
- Partials     8059     8061       +2     
Flag Coverage Δ
backend 64.78% <65.62%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Copy link
Contributor

@jahzielv jahzielv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall, but do we need to edit the software table as well? or just software_titles?

@iansltx
Copy link
Member Author

iansltx commented Mar 7, 2025

@jahzielv Just titles. Titles to software are 1:M and the first piece of software (uploaded or ingested) with a given bundle ID "wins" for determining title name, which sometimes results in the wrong name even when subsequent ingested software has the correct name. This allows admins to manually fix these cases.

jahzielv
jahzielv previously approved these changes Mar 7, 2025

```json
{
"name": "2 Chrome 2 Furious.app"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lol

rachaelshaw
rachaelshaw previously approved these changes Mar 7, 2025
@iansltx iansltx dismissed stale reviews from rachaelshaw and jahzielv via c4506d8 March 7, 2025 17:19
@iansltx iansltx merged commit 014f10f into main Mar 7, 2025
37 checks passed
@iansltx iansltx deleted the 26933-software-name-edit branch March 7, 2025 17:36
iansltx added a commit that referenced this pull request Mar 7, 2025
…a bundle ID (#26938)

For #26933.

# 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)
- [x] 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

---------

Co-authored-by: Rachael Shaw <[email protected]>
iansltx added a commit that referenced this pull request Mar 7, 2025
…a bundle ID (#26938)

For #26933.

# 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)
- [x] 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

---------

Co-authored-by: Rachael Shaw <[email protected]>
iansltx added a commit that referenced this pull request Mar 7, 2025
… titles with a bundle ID (#26959)

Merged into `main` in #26938.

Co-authored-by: Rachael Shaw <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants