Comments (3)
This appears to be a limitation of AWS's description format, which contains many assumptions and 'magic' rather than being a purely declarative format such as OpenAPI. The shape "NoSuchKey" is not defined and the key "404" appears nowhere in the S3 description file. It doesn't even seem possible to programmatically deduce this from the SDK code.
This is basically a best-effort conversion, I don't have the time to maintain a set of patches on top of the raw conversions, though I might accept them if someone contributed them.
maybe we don't need to include all error responses here?
I'm not sure I understand why we wouldn't include as much information as we can from the input format?
from aws2openapi.
From my point of view (I'm doing some code generation by this spec), an object {}
means nothing for me and I have to workaround this by ignore self defined 480
statue code. Instead of expanding this magic to users, maybe eliminate them at specs side is a better solution?
from aws2openapi.
I'm not convinced. {}
is the empty schema and allows everything. Why do you have to remove the dummy error codes? We want to indicate these errors are possible, even if we cannot (yet) map them fully.
from aws2openapi.
Related Issues (20)
- Duplicate Operation Paging Parameters in S3
- The info.contact.x-twitter field causes openapi-generator to fail HOT 7
- The "members" attribute in the AWS service definition is literally a list of "member" objects HOT 7
- Add tests using moto and pyopenapi HOT 6
- Unexpected "get" requests in generated openapi spec HOT 2
- text/xml in iam spec instead of application/xml, which is what the OpenAPI 3.0 spec supports HOT 3
- The "operationId" field shouldn't have spaces HOT 2
- Converter missing response mappings HOT 1
- x-amz-meta- is wrong for AWS S3 PutObject API HOT 1
- Body in PutObject, UploadPart API's type should by string instead of object HOT 2
- S3 API's error not handled correctly HOT 1
- Incorrect usage of additional properties besides $ref for EC2 OpenAPI3 Swagger file HOT 1
- Openapi for endpoints that have pagination end up with duplicate parameters HOT 1
- Incorrect variable type defined in the yaml file
- unexpected multi-type 'allOff' references in runtime.lex.v2 spec
- Query parameters array "serialization" strategy HOT 5
- Support signatureVersion: bearer
- Exception definitions not included
- Duplicate entries in Servers Object
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aws2openapi.