Api handler implementation for osupdaterun resource in apiv2#253
Merged
daniele-moro merged 30 commits intomainfrom Jun 13, 2025
Merged
Api handler implementation for osupdaterun resource in apiv2#253daniele-moro merged 30 commits intomainfrom
daniele-moro merged 30 commits intomainfrom
Conversation
SushilLakra
requested review from
Andrea-Campanella,
Paiadhithi,
PalashGoelIntel,
cjnolan,
damiankopyto,
daniele-moro,
ikyrycho,
jkossak,
krishnajs,
ktaube26,
niket-intc,
osinstom,
pierventre,
raphaelvrosa,
rranjan3,
soniabha-intc,
sunil-parida,
tmatenko and
zdw
as code owners
Contributor
daniele-moro
left a comment
daniele-moro
left a comment
There was a problem hiding this comment.
I've reviewed only the apiv2 content. I believe this is built on top of another PR.
…icts in inventory
…open-edge-platform/infra-core into api-handler-impl-osupdaterun-br
…open-edge-platform/infra-core into api-handler-impl-osupdaterun-br
daniele-moro
approved these changes
Jun 13, 2025
Co-authored-by: Daniele Moro <9449199+daniele-moro@users.noreply.github.com>
…open-edge-platform/infra-core into api-handler-impl-osupdaterun-br
daniele-moro
approved these changes
Jun 13, 2025
…open-edge-platform/infra-core into api-handler-impl-osupdaterun-br
daniele-moro
approved these changes
Jun 13, 2025
jkossak
approved these changes
Jun 13, 2025
krishnajs
approved these changes
Jun 13, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Api handler implementation for osupdaterun resource in apiv2
Fixes ITEP-67236
OS Update Run: stores the information about the update job that run on the Edge Node. This resource is created when the update is started, and stores information about what happened in the Edge Node during the Update. If there are concerns about the size of this table, we can add retention policies for this resource.
status: stores the short description of what happened during the update.
status_indicator: enum field, moder status indicator:
STATUS_INDICATION_ERROR: an error happened during the update.
STATUS_INDICATION_IN_PROGRESS: unused, the progress about the update is kept into the update_status field of the Instance.
STATUS_INDICATION_IDLE: the update was successful.
status_timestamp: timestamp of the last status update. Overlaps with the end_time, but it's kept for consistency with Modern Status. Also, could be used in the future, if we deprecate the Instance update_status.
status_details: detailed description of what happend during the update. For example, the list of packages that were installed or updated, or the reason why the Immutable OS update failed.
start_time: timestamp of when the update job started.
end_time: timestamp of when the update job ended.
applied_policy: the policy that was applied during the update. Provides information of what was the target Update Policy for this update.
Fields should all be read-only from API. ONLY get, delete available
Any Newly Introduced Dependencies
Please describe any newly introduced 3rd party dependencies in this change. List their name, license information and how they are used in the project.
How Has This Been Tested?
Tests will be done using another Jira Tasks.
Checklist: