jasonrush / psasanaapi

PowerShell module to interact with the Asana API

PSAsanaAPI

Another PowerShell module to interact with the Asana API. This is still very alpha, but I hope to make it a much more feature-rich and thorough implementation than any others I've found to date (as time allows, that is).

Usage

The module is currently designed to authenticate by using a copy of your Asana Personal Access Token stored in an environment variable. Once the token is stored in the variable, all PSAsanaAPI functions should be usable.

Instructions on how to generate a Personal Access Token within Asana can be found here: https://asana.com/guide/help/api/api#gl-access-tokens

PS> $env:AsanaPersonalAccessToken = '1/97912xxxxxxxxxx:xxxxxxxxxx287ebe7fc6b5xxxxxxxxxx'
PS> Get-Workspace


gid              name                resource_type
---              ----                -------------
97913xxxxxxxxxx  JasonRush           workspace
110795xxxxxxxxxx JasonsPersonalStuff workspace


PS>

psasanaapi's Issues

-Name should generally be mutually exclusive from -ReturnRaw

I've looked at using [ValidateScript({-not $ReturnRaw})] but this is not well documented and does not seem to support the [switch] type (always returns nothing). Need to figure out a way to throw an error/etc if both parameters are used.

This may apply to other parameters, as well.

PowerShell for Asana

Hi Jason, we're implementing Asana this year. As I like to see how I can leverage PowerShell, I found your module. Thanks for putting this out there. I know you said it was alpha. Are you still using this module? If so, do you have a newer version? And would you like some help? Thanks, Bill

Documentation files (.md) have not been created or populated

Examples in comment-based help are wrong

Many examples in the comment-based help (in the heading of each function .ps1 file) are completely wrong (for the wrong function when a .ps1 file was copied) or have old/invalid syntax from initial creation/testing.

Need to figure out how to complete unit tests that are not dependent on personal Asana account

I have not created much in the way of unit tests so far as I don't have a good sandbox solution set up (and haven't even investigated it yet). Need to figure out if there is a reasonable way that unit tests could be safely/successfully run by the public without giving access to personal Asana account/projects/tasks.