[swagger]containerApps.listSecrets throws response code 204 as an error
See original GitHub issue- @azure/arm-appcontainers:
- *^1.0.0:
Describe the bug
client.containerApps.listSecrets
considers the 204 response code to be an error. This happens if the container app pinged has no secrets associated with it. It should probably just return an empty array rather than throwing an error.
To Reproduce Steps to reproduce the behavior:
- Call
client.containerApps.listSecrets
on a container app that has no secrets
Expected behavior If the container app has a secret, return the array. If it does not, return an empty array.
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Add any other context about the problem here.
Issue Analytics
- State:
- Created a year ago
- Comments:17 (10 by maintainers)
Top Results From Across the Web
swagger - Unknown response type for the 204 code status
Some responses, such as 204 No Content, have No Body. To indicate the response body is empty, do not specify content for the...
Read more >Describing Responses - Swagger
A response is defined by its HTTP status code and the data returned in the response body and/or headers. Here is a minimal...
Read more >Reference — Podman documentation
This documentation describes the Podman v2.x+ RESTful API. It consists of a Docker-compatible API and a Libpod API providing support for Podman's unique ......
Read more >Issues · Azure/azure-sdk-for-js · GitHub
listSecrets function doesn't accept rgName parameter App Services customer-reported Issues that are reported by GitHub users external to the Azure organization.
Read more >Bug report: 202 and 204 response result in error t...
Exactly the same service from the connector works in Flow. It seems that PowerApps care about the response and do not like 202/204...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Verified that this is fixed. Thanks!
@nturinski we reproduced the errors in local and these two deletions are identified as client errors. We are working on the fixes and will let you know once ready!
Please notice this error is different from the one in
client.containerApps.listSecrets
which is a swagger issue we need to work with service team to fix.