Frederic Bonin

As mentioned in this ticket, I added a new target named "target-cgw" that will allow targeting the CGW. You can use it like this : { "name": "core", "routes": [...

Fixed here : https://github.com/aws-samples/aws-secure-environment-accelerator/pull/878 As mentioned in the PR, I did not use the remote TGW name since it might lead to collision : name would be tgw_associate_Main_core and tgw_associate_Main_core...

Fixed in this PR : https://github.com/aws-samples/aws-secure-environment-accelerator/pull/877

Fixed in this PR : https://github.com/aws-samples/aws-secure-environment-accelerator/pull/876

See this issue for a workaround : https://github.com/cdimascio/express-openapi-validator/issues/820

See this issue for a workaround : https://github.com/cdimascio/express-openapi-validator/issues/820

I will add this next, thank you for the report !

Implemented : > Expose a console class that can be imported and created, just like node. This however would require read and write streams as inputs which is a bit...

The version 5.0.2 with the fix here : https://github.com/cdimascio/express-openapi-validator/commit/e5cb5d68607fa0ad37c074363c471bb11d7791bb allows the use of this format to avoid the issue above : ``` requestBody: content: multipart/form-data: schema: type: object properties: document:...