Azure / Azure/azure-rest-api-specs
Managed HSM: The status of LRO operation of `HSMSecurityDomain_Download` have be `Succeeded` not `Success`
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 5.9k
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 444
Description
Hi, when i try to activate a manged HSM by API, the response of a LRO as below whick not obey the Azure
What i got fron LRO query:
```
{
"status": "Success",
"status_details": "The resource is active."
}
```
related operation in spec:
https://github.com/Azure/azure-rest-api-specs/blob/ba9f30eed00b61ebb1ceedecd65a8ce82c81609b/specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.4/securitydomain.json#L59-L66
but according to
https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/async-operations
and from autorest SDK const definition, it only has the `Succeeded` not `Success`:
https://github.com/Azure/go-autorest/blob/ee71315119d4d7088d74ca9fcbc7301ce2ed2bc1/autorest/azure/async.go#L37-L42
```go
const (
operationInProgress string = "InProgress"
operationCanceled string = "Canceled"
operationFailed string = "Failed"
operationSucceeded string = "Succeeded"
)
```
Contributor guide
Research direction
Inspect specification/keyvault/data-plane/Microsoft.KeyVault/stable/7.4/securitydomain.json at the HSMSecurityDomain_Download operation, then compare its LRO status schema with the Azure async-operations guidance and the referenced autorest/azure/async.go constants. Confirm the intended status spelling and validate that the specification consistently represents the completed operation as Succeeded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100