Use wrangler deploy artifacts for deployment URLs

[tsteckenborn]

Hi all,
I was wondering why I see some of my environment variables as deployment urls. I would argue that the coding here is not robust enough as I now always get, for example, the posthog endpoint I set as a variable (because it may be us or eu) as my deployment url:

wrangler-action/src/index.ts

Lines 343 to 349 in b2be7ab

	// If this is a workers or pages deployment, try to extract the deployment URL
	let deploymentUrl = "";
	const deploymentUrlMatch = stdOut.match(/https?:\/\/[a-zA-Z0-9-./]+/);
	if (deploymentUrlMatch && deploymentUrlMatch[0]) {
	deploymentUrl = deploymentUrlMatch[0].trim();
	setOutput("deployment-url", deploymentUrl);
	}

Would be nice if this could be improved.

[nprogers]

This is a bug where wrangler-action is picking up the first url listed in environment variables. We need to create a PR to use deployment metadata instead. Updating this issue to reflect what work needs to be done.

[michael-land]

I still have this issue due to it extracts the first URL from stdout, which is https://github.com/cloudflare/workers-sdk/tree/main/packages/wrangler/telemetry.md

verison:

    "wrangler": "3.99.0"
    "wrangler-action": "v3.13.0"

/usr/local/bin/npx wrangler deploy
  Cloudflare collects anonymous telemetry about your usage of Wrangler. Learn more at https://github.com/cloudflare/workers-sdk/tree/main/packages/wrangler/telemetry.md
   ⛅️ wrangler 3.99.0

[michael-land]

In my case, the workaround is to add WRANGLER_SEND_METRICS: false to the environment.