v3.2

Conch API release v3.2

PR #1074 - v3.1.2 minor fixes

• Branch: ether/v3.1.1-minor-fixes

• Revision: 0298194

• Labels: bug
  People

---

• Author: karenetheridge

• Merged By: karenetheridge

• Merged: 2020-12-10T19:43:03Z

Commits

• 5dd0ec - fix handling of these exceptions
• 823c6b - two spaces good, four spaces bad

---

PR #1076 - also add title, readOnly annotations to HardwareProducts

• Branch: ether/hardware_products-annotations

• Revision: 7a808dc

• Labels: api

...matching the changes made in 6d29f50 (PR #1069)

People

• Author: karenetheridge

• Merged By: karenetheridge

• Merged: 2021-01-04T20:24:04Z

Commits

• 56fecf - also add title, readOnly annotations to HardwareProducts

---

PR #1075 - v3.2: json schema CRUD endpoints

• Branch: ether/v3.2-json_schema-crud-endpoints

• Revision: b5217d8

• Labels: api, database, enhancement, v3.next

• new json_schema database table

• new endpoints for creating, deleting, fetching json schemas
  POST /json_schema/:type/:name
  GET /json_schema/:id
  GET /json_schema/:type/:name/:version
  GET /json_schema/:type/:name/latest
  DELETE /json_schema/:id and /json_schema/:type/:name/:version (not /latest)

• changes to /json_schema/hardware_product/specification and individual hardware_product.specification fields are cross-checked against each other

People

• Author: karenetheridge

• Merged By: karenetheridge

• Merged: 2021-01-04T22:02:49Z

Commits

• 9e2ec2 - update JSD2 and Mojolicious
• 3cedaa - rename this action, in preparation for adding more
• 8ce3c0 - add json_schema table
• 30c6d3 - endpoints for creating, deleting, fetching json schemas
• 38e0ca - coordinate changes to /json_schema/hardware_product/specification and individual hardware_product.specification fields
• 7cd410 - allow fetching JSON Schemas (body, or metadata) even when deactivated

---

PR #1077 - generate new validation results

• Branch: ether/v3.2-new-validation_results

• Revision: 23c8316

• Labels: api, breaking, database, enhancement, needs-shell, needs-ui, v3.next

Support the possibility of new-style validation results in the endpoints that return them, and move aside the legacy validation tables.

Attention clients: device SSJ18115546 in staging will contain both old- and new-style validation results, for the purposes of testing.

People

• Author: karenetheridge

• Merged By: karenetheridge

• Merged: 2021-01-05T22:49:04Z

Commits

• 03f986 - move aside old validation results, preserving contents
• c95c85 - move aside old validation tables
• a28628 - create new validation_result and validation_state_member tables
• f81243 - add title annotations for legacy validation results
• 2707ae - also include new validation results in validation_state queries
• c6c5e5 - development tool for creating new validation_results for testing

---