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

finalize plans for uniquely identifying hardware (via sku or other) #960

Open
karenetheridge opened this issue Dec 2, 2019 · 0 comments
Open

finalize plans for uniquely identifying hardware (via sku or other) #960

karenetheridge opened this issue Dec 2, 2019 · 0 comments
Labels
api database involves database schema or config changes, or non-trivial query authoring high priority High voltage. v3.0 features, big changes for api v3.0

Comments

@karenetheridge
Copy link
Contributor

karenetheridge commented Dec 2, 2019 •
edited
Loading

v3.0 code as it exists in master today requires that all new hardware_products be given a unique sku, and device reports must contain a sku (which is used to look up the actual hardware a device is using, for validation purposes). This requirement may not be the best decision if some hardware (notably switches) aren't assigned skus and aren't as customizable as servers when provisioned.

Need to come to a decision on this, and adjust code/api restrictions, before 3.0.0 can go final.
@karenetheridge karenetheridge added api high priority High voltage. database involves database schema or config changes, or non-trivial query authoring v3.0 features, big changes for api v3.0 labels Dec 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
api database involves database schema or config changes, or non-trivial query authoring high priority High voltage. v3.0 features, big changes for api v3.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karenetheridge