Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

select base device report conformance via content negotiation #1001

Open
karenetheridge opened this issue Apr 21, 2020 · 2 comments
Open

select base device report conformance via content negotiation #1001

karenetheridge opened this issue Apr 21, 2020 · 2 comments
Labels
blocked blocked on something else being deployed first enhancement extends current functionality needs-reporter needs accompanying changes in conch-reporter/livesys v3.next features, big changes for api v3.<next> validation

Comments

@karenetheridge
Copy link
Contributor

As we change device report formats, we can select the base schema conformance via:
Content-Type: application/schema-instance+json; schema="https://conch.joyent.us/json_schema/request/base_device_report_schema_v1.2"
@karenetheridge karenetheridge added enhancement extends current functionality blocked blocked on something else being deployed first v3.next features, big changes for api v3.<next> labels Apr 21, 2020
@karenetheridge
Copy link
Contributor Author

Blocked on #943, and also on the JSON Schema specification figuring out what to do here (draft 2019-09 says to do what I wrote above, but https://www.w3.org/TR/dx-prof-conneg/ seems to be modifying the syntax a bit).

@karenetheridge karenetheridge added needs-reporter needs accompanying changes in conch-reporter/livesys validation labels Jun 25, 2020
@karenetheridge
Copy link
Contributor Author

We can also use this to switch between different report formats and validation types, e.g. "preflight from livesys" vs. "production postflight from serengeti".

@karenetheridge karenetheridge mentioned this issue Oct 2, 2020
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
blocked blocked on something else being deployed first enhancement extends current functionality needs-reporter needs accompanying changes in conch-reporter/livesys v3.next features, big changes for api v3.<next> validation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karenetheridge