When running wrangler deploy add a OPEN_NEXT_DEPLOY environment variable to let wrangler know that it is being run by open-next (#1023)

Author: dario-piotrowicz

.changeset/mighty-heads-shine.md

@@ -0,0 +1,5 @@
+---
+"@opennextjs/cloudflare": patch
+---
+
+When running `wrangler deploy` add a `OPEN_NEXT_DEPLOY` environment variable to let wrangler know that it is being run by open-next

packages/cloudflare/src/cli/commands/deploy.ts

@@ -56,6 +56,13 @@ export async function deployCommand(args: WithWranglerArgs<{ cacheChunkSize?: nu
 		],
 		{
 			logging: "all",
+			env: {
+				// If we are running the deploy command we set this OPEN_NEXT_DEPLOY environment variable
+				// to let `wrangler deploy` know that it is being run from open-next. We do this because
+				// otherwise `wrangler deploy` run in an open-next project would call
+				// `opennextjs-cloudflare deploy` (thus causing an unwanted recursion).
+				OPEN_NEXT_DEPLOY: "true",
+			},
 		}
 	);
 }

packages/cloudflare/src/cli/utils/run-wrangler.ts

@@ -13,6 +13,7 @@ type WranglerOptions = {
 	environment?: string;
 	configPath?: string;
 	logging?: "all" | "error";
+	env?: Record<string, string>;
 };
 
 /**
@@ -79,6 +80,7 @@ export function runWrangler(options: BuildOptions, args: string[], wranglerOpts:
 			stdio: shouldPipeLogs ? ["ignore", "pipe", "pipe"] : "inherit",
 			env: {
 				...process.env,
+				...wranglerOpts.env,
 				// `.env` files are handled by the adapter.
 				// Wrangler would load `.env.<wrangler env>` while we should load `.env.<process.env.NEXTJS_ENV>`
 				// See https://opennext.js.org/cloudflare/howtos/env-vars