Skip to content

Invoke Command (az devops invoke) yields type error #644

@adamgilfix

Description

@adamgilfix

Problem: Issue with https://github.com/github/awesome-copilot/blob/main/skills/azure-devops-cli/SKILL.md, where leveraging the az devops invoke command to make a corresponding REST API call generates a type error.

Example where org has already been configured and actual project and work item ID are input into the GET call here:
az devops invoke --area wit --resource comments --route-parameters project=${PROJECT} workItemId=${ITEM_ID} --http-method GET --api-version "7.1-preview.4" --accept-media-type application/json

Resulting Error: could not convert string to float: '7.1.4'

Proposed Solution: Fix the log around the client.send(...) input with + ';api-version=' + negotiated_version so that negotiated_version is simply a string value passed by the user (rather than trying to float-convert the user input)

Note: I tried various workarounds and the best bet was a direct az rest API call, but that requires separate login/authentication that makes the az devops automation a lot more manual and less robust.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions