@constructive-io/bucket-provisioner 0.26.0 → 0.27.0

package/README.md

@@ -196,11 +196,6 @@ belongs to one database at one scope, and there is no global bucket namespace to
 prefix into. Each readable component has its own budget, so a long scope cannot
 crowd out the database label, and the digest covers the untruncated identity.
 
-#### `mintPhysicalBucketName(prefix, databaseId, bucketKey)`
-
-The prefixed policy — `{prefix}-{bucketKey}-{digest}` — for a deployment that
-names its own bucket namespace.
-
 ### Policy Builders
 
 Standalone functions for generating S3 policy documents.

package/esm/index.d.ts

@@ -29,7 +29,7 @@
 export type { BucketProvisionerOptions } from './provisioner';
 export { BucketProvisioner } from './provisioner';
 export type { PhysicalBucketIdentity } from './naming';
-export { mintPhysicalBucketName, physicalBucketName } from './naming';
+export { physicalBucketName } from './naming';
 export { createS3Client } from './client';
 export type { BucketPolicyDocument, BucketPolicyStatement, PublicAccessBlockConfig, } from './policies';
 export { buildCloudFrontOacPolicy, buildPresignedUrlIamPolicy, buildPublicReadPolicy, getPublicAccessBlock, } from './policies';

package/esm/index.js

@@ -27,7 +27,7 @@
  * ```
  */
 export { BucketProvisioner } from './provisioner';
-export { mintPhysicalBucketName, physicalBucketName } from './naming';
+export { physicalBucketName } from './naming';
 // S3 client factory
 export { createS3Client } from './client';
 export { buildCloudFrontOacPolicy, buildPresignedUrlIamPolicy, buildPublicReadPolicy, getPublicAccessBlock, } from './policies';

package/esm/naming.d.ts

@@ -14,24 +14,13 @@ export interface PhysicalBucketIdentity {
  *
  * This is the policy for a platform-provisioned bucket, and it takes no prefix
  * because there is no global bucket namespace to prefix into: a bucket belongs
- * to one database at one scope, and that is what its name should say. Callers
- * derive names from here rather than composing a prefix of their own, so the
- * policy can change in one place — and an already-provisioned bucket never
- * consults it at all, since the row's recorded `physical_name` is authoritative.
+ * to one database at one scope, and that is what its name should say. The
+ * reconciler derives names from here rather than composing a prefix of its own,
+ * and consumers of a bucket row never consult this policy: the recorded
+ * `physical_name` is authoritative.
  *
  * The scope is part of the digested identity untruncated, so two scopes of one
  * database that declare the same bucket key stay distinct even when their
  * readable labels truncate to the same thing.
  */
 export declare function physicalBucketName(identity: PhysicalBucketIdentity): string;
-/**
- * The prefixed physical-bucket naming policy:
- * `{prefix}-{bucketKey}-{digest}` (e.g. `myapp-public-3f9c1a2b7e04`).
- *
- * For a deployment that names its own bucket namespace — a single-app
- * installation, or the presigned-upload (lazy) path meeting a bucket an app
- * configured. A platform-provisioned bucket uses {@link physicalBucketName}
- * instead, whose components come from the bucket row rather than from
- * deployment config.
- */
-export declare function mintPhysicalBucketName(prefix: string, databaseId: string, bucketKey: string): string;

package/esm/naming.js

@@ -5,9 +5,6 @@ const MAX_BUCKET_NAME_LENGTH = 63;
 const MIN_BUCKET_NAME_LENGTH = 3;
 /** Hex characters of the identity digest kept as the uniqueness tail. */
 const IDENTITY_DIGEST_LENGTH = 12;
-/** Readable budget: how much of the name the prefix and key may each occupy. */
-const PREFIX_BUDGET = 20;
-const BUCKET_KEY_BUDGET = 63 - IDENTITY_DIGEST_LENGTH - PREFIX_BUDGET - 3;
 /**
  * Readable budgets for a name minted from a bucket's own identity.
  *
@@ -74,10 +71,10 @@ function assembleBucketName(readable, identity, describeIdentity) {
  *
  * This is the policy for a platform-provisioned bucket, and it takes no prefix
  * because there is no global bucket namespace to prefix into: a bucket belongs
- * to one database at one scope, and that is what its name should say. Callers
- * derive names from here rather than composing a prefix of their own, so the
- * policy can change in one place — and an already-provisioned bucket never
- * consults it at all, since the row's recorded `physical_name` is authoritative.
+ * to one database at one scope, and that is what its name should say. The
+ * reconciler derives names from here rather than composing a prefix of its own,
+ * and consumers of a bucket row never consult this policy: the recorded
+ * `physical_name` is authoritative.
  *
  * The scope is part of the digested identity untruncated, so two scopes of one
  * database that declare the same bucket key stay distinct even when their
@@ -91,19 +88,3 @@ export function physicalBucketName(identity) {
         readableComponent(bucketKey, IDENTITY_KEY_BUDGET),
     ], `${scope}/${databaseId}/${bucketKey}`, `key "${bucketKey}" at scope "${scope}"`);
 }
-/**
- * The prefixed physical-bucket naming policy:
- * `{prefix}-{bucketKey}-{digest}` (e.g. `myapp-public-3f9c1a2b7e04`).
- *
- * For a deployment that names its own bucket namespace — a single-app
- * installation, or the presigned-upload (lazy) path meeting a bucket an app
- * configured. A platform-provisioned bucket uses {@link physicalBucketName}
- * instead, whose components come from the bucket row rather than from
- * deployment config.
- */
-export function mintPhysicalBucketName(prefix, databaseId, bucketKey) {
-    return assembleBucketName([
-        readableComponent(prefix, PREFIX_BUDGET),
-        readableComponent(bucketKey, BUCKET_KEY_BUDGET),
-    ], `${prefix}/${databaseId}/${bucketKey}`, `key "${bucketKey}"`);
-}

package/index.d.ts

@@ -29,7 +29,7 @@
 export type { BucketProvisionerOptions } from './provisioner';
 export { BucketProvisioner } from './provisioner';
 export type { PhysicalBucketIdentity } from './naming';
-export { mintPhysicalBucketName, physicalBucketName } from './naming';
+export { physicalBucketName } from './naming';
 export { createS3Client } from './client';
 export type { BucketPolicyDocument, BucketPolicyStatement, PublicAccessBlockConfig, } from './policies';
 export { buildCloudFrontOacPolicy, buildPresignedUrlIamPolicy, buildPublicReadPolicy, getPublicAccessBlock, } from './policies';

package/index.js

@@ -28,11 +28,10 @@
  * ```
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.ProvisionerError = exports.buildTempCleanupRule = exports.buildAbortIncompleteMultipartRule = exports.buildUploadCorsRules = exports.buildPrivateCorsRules = exports.getPublicAccessBlock = exports.buildPublicReadPolicy = exports.buildPresignedUrlIamPolicy = exports.buildCloudFrontOacPolicy = exports.createS3Client = exports.physicalBucketName = exports.mintPhysicalBucketName = exports.BucketProvisioner = void 0;
+exports.ProvisionerError = exports.buildTempCleanupRule = exports.buildAbortIncompleteMultipartRule = exports.buildUploadCorsRules = exports.buildPrivateCorsRules = exports.getPublicAccessBlock = exports.buildPublicReadPolicy = exports.buildPresignedUrlIamPolicy = exports.buildCloudFrontOacPolicy = exports.createS3Client = exports.physicalBucketName = exports.BucketProvisioner = void 0;
 var provisioner_1 = require("./provisioner");
 Object.defineProperty(exports, "BucketProvisioner", { enumerable: true, get: function () { return provisioner_1.BucketProvisioner; } });
 var naming_1 = require("./naming");
-Object.defineProperty(exports, "mintPhysicalBucketName", { enumerable: true, get: function () { return naming_1.mintPhysicalBucketName; } });
 Object.defineProperty(exports, "physicalBucketName", { enumerable: true, get: function () { return naming_1.physicalBucketName; } });
 // S3 client factory
 var client_1 = require("./client");

package/naming.d.ts

@@ -14,24 +14,13 @@ export interface PhysicalBucketIdentity {
  *
  * This is the policy for a platform-provisioned bucket, and it takes no prefix
  * because there is no global bucket namespace to prefix into: a bucket belongs
- * to one database at one scope, and that is what its name should say. Callers
- * derive names from here rather than composing a prefix of their own, so the
- * policy can change in one place — and an already-provisioned bucket never
- * consults it at all, since the row's recorded `physical_name` is authoritative.
+ * to one database at one scope, and that is what its name should say. The
+ * reconciler derives names from here rather than composing a prefix of its own,
+ * and consumers of a bucket row never consult this policy: the recorded
+ * `physical_name` is authoritative.
  *
  * The scope is part of the digested identity untruncated, so two scopes of one
  * database that declare the same bucket key stay distinct even when their
  * readable labels truncate to the same thing.
  */
 export declare function physicalBucketName(identity: PhysicalBucketIdentity): string;
-/**
- * The prefixed physical-bucket naming policy:
- * `{prefix}-{bucketKey}-{digest}` (e.g. `myapp-public-3f9c1a2b7e04`).
- *
- * For a deployment that names its own bucket namespace — a single-app
- * installation, or the presigned-upload (lazy) path meeting a bucket an app
- * configured. A platform-provisioned bucket uses {@link physicalBucketName}
- * instead, whose components come from the bucket row rather than from
- * deployment config.
- */
-export declare function mintPhysicalBucketName(prefix: string, databaseId: string, bucketKey: string): string;

package/naming.js

@@ -1,7 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.physicalBucketName = physicalBucketName;
-exports.mintPhysicalBucketName = mintPhysicalBucketName;
 const crypto_1 = require("crypto");
 /** S3's hard ceiling on a bucket name. */
 const MAX_BUCKET_NAME_LENGTH = 63;
@@ -9,9 +8,6 @@ const MAX_BUCKET_NAME_LENGTH = 63;
 const MIN_BUCKET_NAME_LENGTH = 3;
 /** Hex characters of the identity digest kept as the uniqueness tail. */
 const IDENTITY_DIGEST_LENGTH = 12;
-/** Readable budget: how much of the name the prefix and key may each occupy. */
-const PREFIX_BUDGET = 20;
-const BUCKET_KEY_BUDGET = 63 - IDENTITY_DIGEST_LENGTH - PREFIX_BUDGET - 3;
 /**
  * Readable budgets for a name minted from a bucket's own identity.
  *
@@ -78,10 +74,10 @@ function assembleBucketName(readable, identity, describeIdentity) {
  *
  * This is the policy for a platform-provisioned bucket, and it takes no prefix
  * because there is no global bucket namespace to prefix into: a bucket belongs
- * to one database at one scope, and that is what its name should say. Callers
- * derive names from here rather than composing a prefix of their own, so the
- * policy can change in one place — and an already-provisioned bucket never
- * consults it at all, since the row's recorded `physical_name` is authoritative.
+ * to one database at one scope, and that is what its name should say. The
+ * reconciler derives names from here rather than composing a prefix of its own,
+ * and consumers of a bucket row never consult this policy: the recorded
+ * `physical_name` is authoritative.
  *
  * The scope is part of the digested identity untruncated, so two scopes of one
  * database that declare the same bucket key stay distinct even when their
@@ -95,19 +91,3 @@ function physicalBucketName(identity) {
         readableComponent(bucketKey, IDENTITY_KEY_BUDGET),
     ], `${scope}/${databaseId}/${bucketKey}`, `key "${bucketKey}" at scope "${scope}"`);
 }
-/**
- * The prefixed physical-bucket naming policy:
- * `{prefix}-{bucketKey}-{digest}` (e.g. `myapp-public-3f9c1a2b7e04`).
- *
- * For a deployment that names its own bucket namespace — a single-app
- * installation, or the presigned-upload (lazy) path meeting a bucket an app
- * configured. A platform-provisioned bucket uses {@link physicalBucketName}
- * instead, whose components come from the bucket row rather than from
- * deployment config.
- */
-function mintPhysicalBucketName(prefix, databaseId, bucketKey) {
-    return assembleBucketName([
-        readableComponent(prefix, PREFIX_BUDGET),
-        readableComponent(bucketKey, BUCKET_KEY_BUDGET),
-    ], `${prefix}/${databaseId}/${bucketKey}`, `key "${bucketKey}"`);
-}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@constructive-io/bucket-provisioner",
-  "version": "0.26.0",
+  "version": "0.27.0",
   "author": "Constructive <developers@constructive.io>",
   "description": "S3-compatible bucket provisioning library — create buckets, configure privacy policies, CORS, and access controls",
   "main": "index.js",
@@ -44,5 +44,5 @@
     "storage",
     "constructive"
   ],
-  "gitHead": "ec6638bb4a06080919cee7e9ebf48306a2535f2f"
+  "gitHead": "77d58bb93796be91d4e00156bb6847392584d3bc"
 }