@celigo/api-specs 0.2.96 → 0.2.97
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/lookupcache.yml +28 -12
- package/package.json +1 -1
- package/schemas.json +1 -1
package/dist/lookupcache.yml
CHANGED
|
@@ -410,9 +410,11 @@ paths:
|
|
|
410
410
|
summary: Upsert entries into a lookup cache
|
|
411
411
|
description: |-
|
|
412
412
|
Writes key-value entries to a lookup cache. Keys that already exist are
|
|
413
|
-
overwritten; new keys are created.
|
|
414
|
-
objects — arrays at the top level are rejected (wrap them in an
|
|
415
|
-
invalid
|
|
413
|
+
overwritten; new keys are created. Values may be null, numbers, booleans,
|
|
414
|
+
strings, or objects — arrays at the top level are rejected (wrap them in an
|
|
415
|
+
object). One invalid entry fails the entire batch and nothing in it is written:
|
|
416
|
+
a bad value returns `400 invalid_value`, and an empty, missing, or over-length
|
|
417
|
+
key returns `400 cache_dynamodb_invalid_key`.
|
|
416
418
|
|
|
417
419
|
The service rejects batches larger than ~1000 entries or ~5 MB of JSON.
|
|
418
420
|
Callers uploading more than that should split their payload; the Celigo CLI
|
|
@@ -979,15 +981,17 @@ components:
|
|
|
979
981
|
LookupCacheDataEntry:
|
|
980
982
|
type: object
|
|
981
983
|
description: |-
|
|
982
|
-
A single key-value pair stored in a lookup cache.
|
|
983
|
-
|
|
984
|
-
|
|
985
|
-
`400 invalid_value "The value provided corresponding to the key: <k> is invalid"
|
|
986
|
-
|
|
987
|
-
(e.g. `{ "items": [...] }`).
|
|
984
|
+
A single key-value pair stored in a lookup cache. Values may be JSON null, number,
|
|
985
|
+
boolean, string, or object, and each is read back with the type it was upserted
|
|
986
|
+
with. Top-level arrays are **rejected** at upsert with
|
|
987
|
+
`400 invalid_value "The value provided corresponding to the key: <k> is invalid"`,
|
|
988
|
+
as are objects that carry their own top-level `key` property; callers that need to
|
|
989
|
+
store an array should wrap it in an object (e.g. `{ "items": [...] }`).
|
|
988
990
|
properties:
|
|
989
991
|
key:
|
|
990
992
|
type: string
|
|
993
|
+
minLength: 1
|
|
994
|
+
maxLength: 255
|
|
991
995
|
description: |-
|
|
992
996
|
Lookup key. Treated as an opaque string by the cache — case-sensitive, no
|
|
993
997
|
normalization. The same cache can hold multiple entries that differ only in
|
|
@@ -997,19 +1001,31 @@ components:
|
|
|
997
1001
|
- ext-customer-12345
|
|
998
1002
|
value:
|
|
999
1003
|
description: |-
|
|
1000
|
-
Value associated with the key.
|
|
1001
|
-
|
|
1002
|
-
|
|
1004
|
+
Value associated with the key. Nested arrays inside an object are fine; a
|
|
1005
|
+
top-level array is rejected — wrap it. Consumers should check the runtime type
|
|
1006
|
+
before use.
|
|
1003
1007
|
oneOf:
|
|
1008
|
+
- title: Null value
|
|
1009
|
+
type: 'null'
|
|
1010
|
+
- title: Number value
|
|
1011
|
+
type: number
|
|
1012
|
+
- title: Boolean value
|
|
1013
|
+
type: boolean
|
|
1004
1014
|
- title: String value
|
|
1005
1015
|
type: string
|
|
1006
1016
|
- title: Object value
|
|
1007
1017
|
type: object
|
|
1008
1018
|
additionalProperties: true
|
|
1009
1019
|
examples:
|
|
1020
|
+
- null
|
|
1021
|
+
- 42
|
|
1022
|
+
- true
|
|
1010
1023
|
- California
|
|
1011
1024
|
- customerId: 0015g00000abc
|
|
1012
1025
|
- ts: '2026-04-22T00:00:00Z'
|
|
1026
|
+
required:
|
|
1027
|
+
- key
|
|
1028
|
+
- value
|
|
1013
1029
|
LookupCacheDataUpsertRequest:
|
|
1014
1030
|
type: object
|
|
1015
1031
|
description: |-
|
package/package.json
CHANGED