azd rest command

[jongio]

az has a rest command that automatically adds necessary authentication heads to rest calls using the tokens from az login. This is helpful in filling gaps where REST is required such as calls like this:

    az rest \
          --method PATCH \
          --uri "https://graph.microsoft.com/v1.0/applications/$apiObjectId" \
          --headers 'Content-Type=application/json' \
          --body "{ identifierUris:.... "

Should we support azd rest to allow these interactions as well?

[jongio]

While automating with azd in hooks needed for a smooth e2e experience, I discovered that I need to call Azure REST APIs to get keys for services.

I could do so with AZ CLI or AZ PWSH, but I would rather do without those dependencies and use AZD instead.

For now, I wrote code to call the Azure REST APIs, but it would be nice if azd had azd rest so I wouldn't have to do that mapping of azd auth token to my manual REST calls.

[vhvb1989]

My recommendation is to create an sdk client for the Rest Service you want to talk to, using either (java, C#, python, node or go).
Then create a hook to invoke your app.

There are many benefits from following this pattern, versus doing the call by yourself (or delegating to a tool like az). For example, you need to parse responses, handle iterators (for listing), LROs, etc.

[jongio]

This is for automation with ps1/sh files where we don't want to build or create a dependency on a SDK or external lib.

[spboyer]

MCP and agentic work in favor of REST