License: MIT license
This is utility to enrich an openapi integration with information specific for the AWS API Gateway. It allows defining route integrations and authorizers to do automatic (re-)imports in API Gateway.
The openapi integration is extended on two parts: - security: optionally, adding one or more authorizers. - paths: extending each method with the associated authorizer and defining an endpoint.
The input to this utility is passed as parameters.
Paths / Integrations
To define routes, the syntax is:
path.PATH=full_uri[,authorizer_name,scopes]*
For example:
path.user.post=http://3.64.241.104:12121/user/post
This will define an endpoint for the route /user/post, using no authorizers. Alternatively, authorizer plus scopes can be specified:
path.user.post=http://3.64.241.104:12121/user/post,authorizer1,user.email,user.id
In this case, it uses the authorizer with name “authorizer1”, with scopes “user.email” and “user.id”
Defining input / output
Three parameters manage the input / output tasks:
-filename: allows to specify the input files to process, and it is possible to repeat this parameter multiple times. It is an error if the designed filename does not exist.
-glob: which supports specifying the input using filename patterns. It is not an error if this pattern matches no names in the file system.
-output-folder: optional, defines the output folder. If not specified, the input files will be overwritten.
Defining the configuration in a separate file
It is possible to specify any configuration parameters in a separate file, using the argument:
configuration=filename
This file should define the parameters in separate lines, using the same syntax. Empty lines and starting with the character # are discarded.
It is possible to specify multiple external configuration files. An example of a single file would be:
# a comment authorizer.name=DubaixCognito,Other authorizer.identity-source=$request.header.Authorization authorizer.audience=2f0m9fcoiejij4316u574aq259,7ac34sujrb8gmvj2b6blpi7ruu authorizer.issuer=https://cognito-idp.eu-west-2.amazonaws.com/eu-west-2_1T9bfKHNp tag.Frontend=http://3.64.241.104:12121/tmp/,DubaixCognito,user.email,user.id path.user.scope2=http://OTHER_PATH:12122/path,Other,user.email
Metadata
Release files for openapi4aws 1.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| openapi4aws-1.2.1.tar.gz | 7.2 kB | Without provenance | Details for openapi4aws-1.2.1.tar.gz |
Release files / openapi4aws-1.2.1.tar.gz
| Download URL | openapi4aws-1.2.1.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ac2a3e42750fccd34b543a840d23212032d9d927547a1ba9da2163ec118567d9
|
|
BLAKE2b-256 checksum How to use checksums |
927f8279ea5da4a8c00ab39c79e6ec426bba3e9d171a640be29a3ec14243b20b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.7.1 importlib_metadata/4.10.0 pkginfo/1.8.2 requests/2.22.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.8.10
|
Security for openapi4aws 1.2.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.