@cat-factory/provider-s3 0.2.272 → 0.2.274
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/README.md +5 -5
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# @cat-factory/provider-s3
|
|
2
2
|
|
|
3
|
-
Opt-in **AWS S3** (or S3-compatible) blob backend for cat-factory's binary artifacts
|
|
3
|
+
Opt-in **AWS S3** (or S3-compatible) blob backend for cat-factory's binary artifacts:
|
|
4
4
|
implements the kernel `BinaryBlobBackend` port over an S3 bucket.
|
|
5
5
|
|
|
6
6
|
## Why this is its own package
|
|
@@ -10,14 +10,14 @@ the **bytes** can go anywhere (Cloudflare R2, the local filesystem, Postgres, or
|
|
|
10
10
|
the heavy `@aws-sdk/client-s3`, so it ships as its own opt-in package that only a deployment
|
|
11
11
|
choosing S3 depends on. Even then, the SDK is imported **lazily on first I/O**, not at module
|
|
12
12
|
load: a facade statically imports `S3BinaryBlobBackend` to wire its container, but a deployment
|
|
13
|
-
that ends up running the `db`/`fs`/no blob backend never pays the SDK's load cost
|
|
13
|
+
that ends up running the `db`/`fs`/no blob backend never pays the SDK's load cost; the SDK is
|
|
14
14
|
pulled in only when an S3 `put`/`get`/`delete` actually executes.
|
|
15
15
|
|
|
16
16
|
## Enabling it
|
|
17
17
|
|
|
18
18
|
The package exports one class:
|
|
19
19
|
|
|
20
|
-
- `S3BinaryBlobBackend
|
|
20
|
+
- `S3BinaryBlobBackend`: a `BinaryBlobBackend` (`put` / `get` / `delete`) constructed from an
|
|
21
21
|
`S3BinaryBlobBackendConfig`.
|
|
22
22
|
|
|
23
23
|
### Node / local facade
|
|
@@ -40,7 +40,7 @@ case 's3':
|
|
|
40
40
|
An account picks the S3 backend (and supplies region / bucket + credentials) in the
|
|
41
41
|
**content-storage settings UI**; the facade builds the backend from that config. Omitting
|
|
42
42
|
`credentials` is intentional and falls back to the **ambient AWS credential chain** (instance
|
|
43
|
-
role, `AWS_*` env)
|
|
43
|
+
role, `AWS_*` env): the right behaviour for a deployment running on AWS with an attached role.
|
|
44
44
|
(The UI requires explicit keys, so the keyless path is only reached by config written through
|
|
45
45
|
another channel.)
|
|
46
46
|
|
|
@@ -71,4 +71,4 @@ artifact's storage key.
|
|
|
71
71
|
Part of cat-factory's opt-in **AWS stack** alongside
|
|
72
72
|
[`@cat-factory/provider-bedrock`](../provider-bedrock) (LLM models) and
|
|
73
73
|
[`@cat-factory/eks`](../eks) (runner + environment backends). Each is independent and registers
|
|
74
|
-
into its own seam
|
|
74
|
+
into its own seam: mix in only what you use.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@cat-factory/provider-s3",
|
|
3
|
-
"version": "0.2.
|
|
3
|
+
"version": "0.2.274",
|
|
4
4
|
"description": "Opt-in AWS S3 blob backend for the Agent Architecture Board's binary-artifact storage abstraction. Implements the kernel BinaryBlobBackend port over an S3 bucket.",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -25,7 +25,7 @@
|
|
|
25
25
|
},
|
|
26
26
|
"dependencies": {
|
|
27
27
|
"@aws-sdk/client-s3": "^3.1101.0",
|
|
28
|
-
"@cat-factory/kernel": "0.
|
|
28
|
+
"@cat-factory/kernel": "0.218.0"
|
|
29
29
|
},
|
|
30
30
|
"devDependencies": {
|
|
31
31
|
"typescript": "7.0.2"
|