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

feat(ota): exposing optional update target of OTA #755

Conversation

lusergit
Copy link
Collaborator

@lusergit lusergit commented Dec 6, 2024

Ota operations expose an optional UpdateTarget. It is a reference to the update target that created the managed ota operation

Closes #356

@lusergit lusergit added this to the v0.10 milestone Dec 6, 2024
@lusergit lusergit requested a review from noaccOS December 6, 2024 11:18
@coveralls
Copy link

coveralls commented Dec 6, 2024

Pull Request Test Coverage Report for Build 8acace251d36bc6ba1c8f69ae7772739e253a0cf-PR-755

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 80.526%

Totals Coverage Status
Change from base Build 472b713309a9a9c2512a3418faefe2482dd0ac51: 0.0%
Covered Lines: 1224
Relevant Lines: 1520

💛 - Coveralls

@lusergit lusergit force-pushed the feat/ota_operation_update_campaign branch from df5086e to 9ae4323 Compare December 6, 2024 14:09
CHANGELOG.md Outdated Show resolved Hide resolved
Ota operations expose an optional `UpdateTarget`. It is a reference to
the update target that created the managed ota operation

Closes edgehog-device-manager#356

Signed-off-by: Luca Zaninotto <[email protected]>
@lusergit lusergit force-pushed the feat/ota_operation_update_campaign branch from 9ae4323 to 8acace2 Compare December 9, 2024 11:47
@davidebriani davidebriani merged commit 2d4403e into edgehog-device-manager:main Dec 9, 2024
8 checks passed
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.

Expose the associated UpdateCampaign (if any) from an OTA Operation
3 participants