Azure / Azure/azure-rest-api-specs

Create Zip Deployment For Static Site Build - Error NotImplemented

Open
#22,267 13 comments 7 reactions 0 assignees View on GitHub
App Services customer-reported needs-team-attention question Service Attention Web Apps
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

I'm trying to call this api [Static Sites - Create Zip Deployment For Static Site Build](https://learn.microsoft.com/en-us/rest/api/appservice/static-sites/create-zip-deployment-for-static-site-build?tabs=HTTP#code-try-0), and building the request with the needed parameters it always gives me an error:

```json
{
"Code": "NotImplemented",
"Message": "The requested method is not implemented.",
"Target": null,
"Details": [
{
"Message": "The requested method is not implemented."
},
{
"Code": "NotImplemented"
},
{
"ErrorEntity": {
"ExtendedCode": "51009",
"MessageTemplate": "The requested method is not implemented.",
"Parameters": [],
"Code": "NotImplemented",
"Message": "The requested method is not implemented."
}
}
],
"Innererror": null
}
```

This is the endpoint I'm calling:
- https://management.azure.com/subscriptions/[**subscription-id-here**]/resourceGroups/TMC/providers/Microsoft.Web/staticSites/Test1/builds/preview/zipdeploy?api-version=2022-03-01

With this json payload (is a static generated website, no need for api):
```json
{
"properties": {
"appZipUrl": "https://*********.blob.core.windows.net/************_output.zip",
"deploymentTitle": "Update index.html",
"provider": "testProvider",
}
}
```

The subscription ID, resource group name and static app name are correct, and the url for the zip exists and is accessible.
Can this be related with something on my request payload?

Contributor guide

Open the contributing guide

Research direction

Start with the linked Static Sites Create Zip Deployment REST API operation and reproduce the request using the endpoint and JSON payload shown. Compare the documented parameters with the service response, then establish whether the API specification or the service behavior is incorrect; done means the request succeeds or the limitation is clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, openapi
Domain
api, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.