ChrisLGardner / PoshBot.AzDos

PoshBot module for working with Azure DevOps via the VSTeam module
MIT License
6 stars 1 forks source link

Having a hard time connecting AzDos (also, AddVSTeamWorkItem seems to be missing WorkItemType) #21

Closed GitMje closed 5 years ago

GitMje commented 5 years ago

Chris: First off, thank you for writing this PoshBot plugin, it's really nice! Secondly, I'm having trouble getting the basic connectivity working, and I'm wondering if there's something basic that I'm missing.

If I run the Set-VSTeamAccount and then run Get-VSTeamWorkItem -id 23119 on the command line, I see the correct result below.

000314-PowerShell

However, if I run the same command in PoshBot, I get the error below:

000313-Slack _ v-bot _ test-bots

Additionally, I see the following in the logs (in reading the error, it doesn't seem to have enough information to track down the cause):

000312-PowerShell

I'm happy to debug this further myself if you can point me in the direction of how to get more diagnostic data out of PoshBot or if I can run it locally somehow.

My vsteam_profiles.json in my ~\ directory contains the following information:

[
    {
        "Name":  "v-bot-profile",
        "URL":  "https://dev.azure.com/DevOps",
        "Type":  "Pat",
        "Pat":  "REDACTED",
        "Token":  "",
        "Version":  "VSTS"
    }
]

My config file for PoshBot contains:

PluginConfiguration = @{
    'PoshBot.AzDos' = @{
      VSTeamProfile = 'v-bot-profile'
    }
  }

Again, I'd be happy to debug the issue myself, if there's a trick to get more detailed error information out of the tool.

I'm excited about getting the tool up and running, again, thanks for creating it.

Also, I wanted to mention that it looks like AddVSTeamWorkItem may be missing the mandatory WorkItemType parameter. I may be missing something, but I don't think it will work without this parameter. I'm happy to put in a pull request if you agree that it's missing.

GitMje commented 5 years ago

I figured out the issue. It turns out that the v-bot-profile was misconfigured with the URL.