History log of /openbmc/entity-manager/schemas/stepwise.json (Results 1 – 3 of 3)
Revision Date Author Comments
# 7d6080db 04-Sep-2024 Patrick Williams <patrick@stwcx.xyz>

json: adjust definitions alias

JSON Schema suggests[1] using "$defs" rather than "definitions" as
the location for reusable definitions in a schema. While, this
isn't strictly required, there is so

json: adjust definitions alias

JSON Schema suggests[1] using "$defs" rather than "definitions" as
the location for reusable definitions in a schema. While, this
isn't strictly required, there is some implication that using it
lends to better schema validation error reporting[2].

Adjust all the schema files to use "$defs" rather than "definitions".

[1]: https://json-schema.org/understanding-json-schema/structuring#defs
[2]: https://github.com/orgs/json-schema-org/discussions/151

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I4b23890950bd2ebb7a7de99fd911fb3c9e0a4dbd

show more ...


# aca73883 22-Feb-2023 Josh Lehan <krellan@google.com>

Add InputUnavailableAsFailed and newer to PID

These apply to both PID and Stepwise, and are the same in both.

Adding InputUnavailableAsFailed, an optional boolean parameter,
already implemented and

Add InputUnavailableAsFailed and newer to PID

These apply to both PID and Stepwise, and are the same in both.

Adding InputUnavailableAsFailed, an optional boolean parameter,
already implemented and merged some time ago:
https://gerrit.openbmc.org/c/openbmc/phosphor-pid-control/+/47606

Also adding two new parameters, implemented but not yet merged.

MissingIsAcceptable, optional, an array of strings:
https://gerrit.openbmc.org/c/openbmc/phosphor-pid-control/+/60888

TempToMargin, optional, an array of numbers:
https://gerrit.openbmc.org/c/openbmc/phosphor-pid-control/+/60303

Signed-off-by: Josh Lehan <krellan@google.com>
Change-Id: I8a4193618e980208883e2f2093d72c2a1fe934ec

show more ...


# 7d05ee59 26-May-2022 Brad Bishop <bradleyb@fuzziesquirrel.com>

schemas: use lower_snake_case for filenames

To be consistent with lower_snake_case source code filenames, use
lower_snake_case for schema file names as well.

Signed-off-by: Brad Bishop <bradleyb@fu

schemas: use lower_snake_case for filenames

To be consistent with lower_snake_case source code filenames, use
lower_snake_case for schema file names as well.

Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: Id5ddeb4152a147229d522ddc0a1376875bfdfc78

show more ...