@stacksjs/ts-cloud 0.9.4 → 0.11.0

package/dist/drivers/shared/remote-failure.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/drivers/shared/sqlite-shared-path.d.ts

@@ -0,0 +1,50 @@
+/**
+ * Infer the shared path for an app whose database is SQLite.
+ *
+ * A release directory is disposable: the next deploy is a NEW directory and the
+ * old one is pruned. Anything the app writes and must keep therefore has to live
+ * in `shared/` and be symlinked in (see {@link import('./releases')}). `.env` is
+ * shared implicitly; everything else has to be declared in `site.sharedPaths`.
+ *
+ * A SQLite database is the one case ts-cloud can work out on its own, because
+ * the connection and the file path are already in the environment it writes to
+ * the box. Left undeclared, the file lands inside the release, and the deploy
+ * after it starts the app on an empty database with no warning — the whole
+ * dataset is one deploy from being orphaned inside a pruned release.
+ *
+ * So: read `DB_CONNECTION`/`DB_DATABASE` out of the site's resolved env, and
+ * when they describe a release-relative SQLite file, share it automatically.
+ * When they say SQLite but do not say where, say so loudly instead of guessing
+ * a filename — a wrong guess would share a path the app never writes and leave
+ * the real database exactly as exposed, while reporting that it is safe.
+ */
+import type { SharedPathEntry } from '@ts-cloud/core';
+/** Is this site's resolved environment pointing at a SQLite database? */
+export declare function usesSqlite(env: Record<string, string | undefined> | undefined): boolean;
+export interface SqliteSharedPathInference {
+    /**
+     * Release-relative path to add to the site's shared paths. Absent when the
+     * app is not on SQLite, the file already survives deploys, or the path could
+     * not be determined.
+     */
+    path?: string;
+    /**
+     * Why nothing could be inferred even though the app IS on SQLite — an
+     * operator-facing sentence naming what to declare. Absent when there is
+     * nothing to worry about.
+     */
+    warning?: string;
+}
+/**
+ * Work out whether a site's SQLite database needs to be added to its shared
+ * paths, given the environment the deploy writes to the box and whatever the
+ * site already declares.
+ */
+export declare function inferSqliteSharedPath(env: Record<string, string | undefined> | undefined, declared?: readonly SharedPathEntry[]): SqliteSharedPathInference;
+/**
+ * The shared-path entries to append for a site's SQLite database — `[]` when
+ * there is nothing to add. Kept separate from {@link inferSqliteSharedPath} so
+ * script builders can splice it in without having to care about the warning,
+ * which only the deploy driver can surface.
+ */
+export declare function sqliteSharedPaths(env: Record<string, string | undefined> | undefined, declared?: readonly SharedPathEntry[]): SharedPathEntry[];

package/dist/drivers/shared/sqlite-shared-path.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/index.d.ts

@@ -50,6 +50,8 @@ export * from './backups';
 export * from './configuration';
 export type { DnsProvider, DnsProviderConfig, DnsRecord, DnsRecordType, DnsRecordResult, CreateRecordResult, DeleteRecordResult, ListRecordsResult, } from './dns';
 export { PROXIABLE_RECORD_TYPES } from './dns';
+export type { MigratedRecord, SkippedRecord, ZoneMigrationPlan, ZoneMigrationReport, ZoneParityReport, } from './dns';
+export { applyZoneMigration, exportRoute53Zone, planZoneMigration, verifyZoneParity, } from './dns';
 export type { DeclaredRecord, DeclaredRecordInput, DeclaredRecordOutcome, DeclaredRecordsReport, } from './dns';
 export * from '@ts-cloud/core';
 export type { S3Bucket, S3BucketPolicy, CloudFrontDistribution, CloudFrontOriginAccessControl, CloudFrontCacheBehavior, CloudFrontOrigin, } from '@ts-cloud/aws-types';