Client update check: pass artifact_provides in body key, instead of in raw body

Description

Acceptance criteria:

  • Start calling v2/deployments/next endpoint from https://tracker.mender.io/browse/MEN-4784

    • Pass artifact_provides (and the special artifact_name and device_type we add to it) in device_provides key as a JSON object.

    • Pass update_control_map as a bool in the top level.

  • Fall back to v1 POST endpoint, then GET endpoint, as before.

  • Unit tests

Affects versions

None

Environment

None

Checklist

Activity

Show:

Kristian AmlieJune 21, 2021 at 9:12 AM

I merged the client part, but we need to decide on what this will mean for versions before I can merge the documentation.

eystein.maloy.stenbergJune 17, 2021 at 6:29 PM

OK, thanks for letting me know.

Kristian AmlieJune 17, 2021 at 1:46 PM

: Sorry, I had to create this one and , and add them to the sprint. Otherwise we will get an inconsistent API which will be hard to fix later!

Fixed

Details

Assignee

Reporter

Labels

Story Points

Priority

Days in progress

2

Sprint

Backlog

yes

Zendesk Support

Checklist

Created June 17, 2021 at 1:39 PM
Updated June 25, 2024 at 11:55 AM
Resolved June 23, 2021 at 8:03 AM