import type { S3Config } from './config.ts';
/**
 * The storage identity of one S3-compatible mount.
 *
 * `cp` and `mv` compare two operands to decide whether they name the same
 * file. Within one mount the mount-relative path answers that; across mounts
 * it does not, since two prefixes can address one store and a move there would
 * copy an object over itself and then unlink the source.
 *
 * Endpoint, bucket and key prefix pin the object namespace. The endpoint
 * matters because the same bucket name on two providers (AWS vs MinIO vs R2)
 * is two different stores. The prefix joins path-like so two mounts whose
 * prefixes nest still resolve to one key once the mount-relative path is
 * appended.
 *
 * Both runtimes call this rather than each writing it out: the node resource
 * had it and the browser one did not, so the same two buckets compared equal
 * under node and distinct under the browser.
 *
 * @param kind the resource kind, which distinguishes the S3-compatible clones
 * @param config the mount's S3 config
 */
export declare function s3StorageId(kind: string, config: S3Config): string;
//# sourceMappingURL=storage_id.d.ts.map