Azure / Azure/azure-rest-api-specs
[BUG] `automation`: Runtime Environment Package GET API missing contentLink properties
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 3.1k
- Forks
- 6k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 432
Description
API Spec link
API Spec version
2024-10-23
Describe the bug
When creating a Runtime Environment Package resource (Microsoft.Automation/automationAccounts/runtimeEnvironments/packages) with contentLink field (including uri, version, and contentHash), the GET API does not return these fields in the response.
This is the same issue as #25538 (which reports the problem for python3Packages) but now also affects the newer runtimeEnvironments/packages resource introduced in api-version 2024-10-23.
Expected behavior
The GET API should return the contentLink field with uri, version, and contentHash properties that were provided during resource creation.
Actual behavior
The contentLink field is completely absent from the GET response, even though it was provided during creation.
Reproduction Steps
- Create a Runtime Environment Package with contentLink:
PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runtimeEnvironments/{runtimeEnvironmentName}/packages/{packageName}?api-version=2024-10-23
{
"properties": {
"contentLink": {
"uri": "https://pypi.org/packages/source/r/requests/requests-2.31.0.tar.gz",
"version": "2.31.0",
"contentHash": {
"algorithm": "sha265",
"value": "07E108A962B81DD9C9BAA89BB47C0F6EE52B29E83758B07795E408D258B2B87A"
}
}
}
}
- Wait for provisioningState to become Succeeded.
- GET the package:
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroup}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/runtimeEnvironments/{runtimeEnvironmentName}/packages/{packageName}?api-version=2024-10-23 - Observe that contentLink is missing from the response properties.
Environment
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the 2024-10-23 specification/automation/resource-manager/Microsoft.Automation/stable/2024-10-23/package.json API definition linked in the issue. Compare the Runtime Environment Package create and GET shapes, then validate the specification; done means GET responses expose the submitted contentLink, including uri, version, and contentHash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100