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

new API: rack-level endpoint that provides validation statuses #993

Open
karenetheridge opened this issue Apr 9, 2020 · 0 comments
Open
Labels
api blocked blocked on something else being deployed first enhancement extends current functionality needs-shell needs accompanying changes in conch-shell needs-ui needs accompanying changes in conch-ui v3.next features, big changes for api v3.<next>

Comments

@karenetheridge
Copy link
Contributor

We need an API, to be exposed in the web and shell UIs as well, which provides a rack-level view of the validation status of each device, including whether the device thinks it is the same type of hardware (from the report) as what we think should be living in that slot.

This might replace GET .../rack/*/assignment if its usecase is similar in the web UI and shell.

(this would also be available as /rack/:long_rack_name_with_room/... as well as /room/:room_id_or_alias/rack/:rack_id_or_name/..., as with all the other rack-level endpoints.)

blocked on validation engine rewrites, and some database schema changes.

@karenetheridge karenetheridge added enhancement extends current functionality api needs-shell needs accompanying changes in conch-shell needs-ui needs accompanying changes in conch-ui blocked blocked on something else being deployed first v3.next features, big changes for api v3.<next> labels Apr 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
api blocked blocked on something else being deployed first enhancement extends current functionality needs-shell needs accompanying changes in conch-shell needs-ui needs accompanying changes in conch-ui v3.next features, big changes for api v3.<next>
Projects
None yet
Development

No branches or pull requests

1 participant