This should be ready to go. Give it a single script and it'll deploy it to the specified Azure Automation account. It will work for my needs, and hopefully it's general enough that it will work for anyone else that wants to deploy a runbook as well.

One thing that I was a little confused about when writing the definition, in what scenario would the $Deployment passed into the script be a set of multiple deployments? The existing scripts all have a line like foreach ($deploy in $Deployment) (as does mine) but I can't find any examples of a deployment that would have multiple deployments that would need the foreach loop.

You know, I've tried to use this and it's actually not very useful. The problem is that there are 5 types of runbooks, but two of the can be PS1 files. For my usecase I can assume they're "Powershell" runbooks but I can't know that someone else hasn't written a bunch of "Powershell Workflow" runbooks instead. So it'd be nice to be able to deploy a whole directory, but you need some way to specify what type each runbook is.

For my own use I was able to take what I learned writing this to deploy my code but I won't be able to use this because I can't figure out a way to generalize it enough for PSDeploy but have the options to make it specific enough for actual use.

Ahh too bad! I'll close this, if someone has use of it, will be sure to point them this way - cheers!