Save Wrangler Command Output to a Variable

[GrantBirki]

Save Wrangler Command Output to a Variable

Please disregard the branch name, I changed what this PR does per @1000hz's suggestions

This pull request enables a more advanced usage of this Action in conjunction with other workflow steps. These changes allow users to gain the ability to parse the wrangler command's output in subsequent workflow steps should they need to.

The @actions/exec package is utilized to save the stdout and stderr streams to variables and then those variables are written to two new Actions outputs when this job completes. These two new outputs are as follows:

• command-output: contains the string results of stdout
• command-stderr: contains the string results of stderr

But wait, there is more! ⭐

Since we are saving the stdout to a variable, it can now be parsed by this Action just a little bit more before exiting. I added in a bonus feature to this PR to detect if the command being run is a deployment for a Cloudflare Pages site or Worker. If it is a deployment, then the deployment-url output gets populated.

• deployment-url: contains the string results of the URL that was deploy (ex: https://<your_pages_site>.pages.dev)

Why?

I personally have several open source projects which I help maintain. We use this Action to deploy our Cloudflare Pages sites. Recently, our workflows for dev environments started breaking. This was a direct result of #210

Here is a resulting Action's log of the failure

This is because we are trying to save the stdout of this Action by piping it to a file. This isn't really the best solution but it worked... at least for a while before it broke. This PR will prevent us from having to use choppy command line hacks in the future.

Being able to capture the output of this command to get the unique dev environment URL for pages deployments is required by our workflows to use it in subsequent workflow steps. This pull request also solves that problem via the new deployment-url output that gets saved as well.

Example 📸

live example workflow -> https://github.com/the-hideout/tarkov-dev/actions/runs/7064233377/job/19231836343

---

resolves: #211

Thanks! ⭐

[1000hz]

Hey @GrantBirki, thanks for the PR. Would your use case be satisfied if we implemented the command-output action output as described in #211?

[GrantBirki]

@1000hz that would be even better! Do you mind if I alter this PR to make all the text that gets written to a file be written to the command-output output instead?

[1000hz]

@GrantBirki that'd be wonderful. Thanks!

[GrantBirki]

@1000hz I have good news, this is ready for review! 🎉

I have tested that all code included in this pull request works:

• source code to my workflows
• passing workflow logs with output results

I managed to fully implement the command-output that you suggested but also with a few bonuses! I also added a command-stderr variable for users to dig into specific error messages that wrangler commands may return in subsequent workflow steps. I also managed to add the deployment-url output that you mentioned in the other issue as well.

Let me know if you have any questions. Thanks!

[1000hz]

Nice work, @GrantBirki! Left a few comments.

[1000hz]

Thanks for the contribution, @GrantBirki!

[GrantBirki]

Thank you! 🎉