bug: AppConfig empty hosted configuration upload causes None.read() InternalError #71
Replies: 2 comments
|
Retested on 2026-10-10 against unmodified Creating a hosted configuration version with an empty body still returns HTTP 500 / Resolved image index: |
|
Hi @AndreKurait, thanks for being proactive with this issue. I have reproduced it on my side and escalated to my engineers for a fix. We will let you know once a fix is live for you to test. Thanks again! |
Uh oh!
There was an error while loading. Please reload this page.
Reproduced on unmodified
localstack/localstack-pro:dev, freshly pulled on 2026-10-10, native linux/amd64:sha256:513f218caf22d1fcb115f055225c96c7140813efcb23e48c9e24b688cdb31cd4sha256:b104c9b43442fba4e1e00ab68c447681b08db6dc6128273d105e1db5c87e5ab32026.10.0.dev97;SERVICES=appconfig; no extensions, source mounts, or custom entrypoint.Uploading a zero-byte hosted configuration with
ContentType=application/octet-streamreturns HTTP 500InternalError:Expected: either accept the zero-byte content if supported, or reject it with the appropriate modeled client error. A supplied empty payload should not cause an internal
None.read()exception. I have not tested the empty-payload acceptance contract against AWS.Minimal reproduction against a disposable LocalStack instance:
A nonempty JSON upload to the same profile succeeds. The test used real boto3 requests with retries disabled. Fixture resources and the disposable container were cleaned up; no production AWS execution is claimed.
All reactions