Skip to content

Add hash_sha256 to example software titles API response#28453

Merged
sgress454 merged 1 commit into
docs-v4.68.0from
sgress454/28433-docs
Apr 24, 2025
Merged

Add hash_sha256 to example software titles API response#28453
sgress454 merged 1 commit into
docs-v4.68.0from
sgress454/28433-docs

Conversation

@sgress454
Copy link
Copy Markdown
Contributor

Related to #28447

sgress454 added a commit that referenced this pull request Apr 24, 2025
# 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)

# Details

To facilitate using the work of
[#23497](#23497) in the new
fleetctl generate-gitops command, we need to be able to retrieve the
hash values of the current software installers for a team. This PR adds
a new `hash_sha256` field to the response for the GET /software/titles
API in order to do that.

# Testing

Updated an existing automated test to check for the presence of the new
field when expected. Other tests still pass without it, as it's omitted
when the underlying `storage_id` db column is null 👍

I verified that the API response is as expected in Fleet:
<img width="361" alt="image"
src="https://github.com/user-attachments/assets/498b0a95-f35c-4ff5-8831-e4c5c68e5f94"
/>

# Docs

See #28453
@sgress454 sgress454 merged commit c975961 into docs-v4.68.0 Apr 24, 2025
6 checks passed
@sgress454 sgress454 deleted the sgress454/28433-docs branch April 24, 2025 17:09
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.

2 participants