import { type RiskyConfigInput } from "../../lib/utils/risky-config-warnings"; import { ProfileConfig } from "../../lib/types/config"; /** * Helper function to display setup command suggestion */ /** * The bucket and verification settings the deployment will actually run with. * * The container reads them from the Benchling secret, and deploy doesn't overwrite an existing * standalone secret, so the deployed secret wins over the local profile when it can be read. */ export declare function deployedRiskySettings(config: ProfileConfig, secretDetails: { userBucket?: string; enableVerification?: boolean; } | null): RiskyConfigInput; /** * Deploy command for v0.7.0 configuration architecture * * Uses new profile-based configuration with deployment tracking. * Uses profile-based configuration. * * v0.10.0: Refactored to call createStack() directly instead of spawning subprocess. * This eliminates environment variable IPC complexity and simplifies testing. * * @module commands/deploy * @version 0.10.0 */ export declare function deployCommand(options: { yes?: boolean; bootstrapCheck?: boolean; requireApproval?: string; profile?: string; stackArn?: string; benchlingSecret?: string; imageTag?: string; region?: string; envFile?: string; force?: boolean; }): Promise; /** * Deploy the Benchling webhook stack * * v0.10.0: Refactored to call createStack() directly instead of using environment variable IPC. * Configuration is passed programmatically through function calls, not subprocess environment. */ export declare function deploy(stackArn: string, benchlingSecret: string, config: ProfileConfig, options: { yes?: boolean; bootstrapCheck?: boolean; requireApproval?: string; profileName: string; imageTag: string; region?: string; envFile?: string; force?: boolean; }): Promise; //# sourceMappingURL=deploy.d.ts.map