Summary of the new feature / enhancement
Currently, for every operation, the engine requests the schema so it can be spawning the same process over and over (or reading it from the manifest over and over). For a set, the engine will perform a test (or synthetic test using get) to validate the input and then the output, then perform the set, validating again, then perform a get to get actual state and validate again. Each validation re-retrieves the JSON Schema
Proposed technical implementation details (optional)
Keep a cache of JSON schema per resource/version. Only retrieve the schema if it's not in the cache. In memory cache only.
Summary of the new feature / enhancement
Currently, for every operation, the engine requests the schema so it can be spawning the same process over and over (or reading it from the manifest over and over). For a
set, the engine will perform atest(or synthetictestusingget) to validate the input and then the output, then perform the set, validating again, then perform agetto get actual state and validate again. Each validation re-retrieves the JSON SchemaProposed technical implementation details (optional)
Keep a cache of JSON schema per resource/version. Only retrieve the schema if it's not in the cache. In memory cache only.