Releases: awslabs/aws-api-gateway-developer-portal
Releases · awslabs/aws-api-gateway-developer-portal
v2.3.3
v2.3.1
Features:
- #210 - Add support for using Cognito hosted UI
- #190 - Modify CFN stack to output custom domain name, if using one
Security changes:
- #211 - Increase Cognito User Pool password policy requirements
- #210 - SSL/HTTPS out of the box by placing a Cloudfront distribution in front of all developer portals
- A later, major revision (breaking change) to the dev portal will make the S3 site URL inaccessible except through Cloudfront; please plan accordingly
Documentation:
v2.3.0
v2.2.4
Unit tests, bug fixes, and documentation improvements
Unit tests
- There's a new unit test suite! Run it with
npm run test
from the project's top-level after runningnpm run get-dependencies
. Note that running the unit tests will require a number of dependencies not required to deploy the dev portal (e.g., a modern version of node and npm, many npm modules, etc). To get coverage reports, runnpm run coverage
.
Bug fixes
- improve state management on sign in and sign out
- clean up left nav bar visuals and wording
- don't attempt to use an api key for "Try it out!" when a given user does not have an api key
- remove version field from swagger ui for api gateway managed apis
- improve "generic" swagger detection
Documentation improvements
v2.2.3
SAR release
The developer portal is available through SAR!
This version includes a few fixes to facilitate that, including a new, shortened README for SAR (README_SAR.md
) and a change to the MarketplaceMeteringRole name.
Release v2.2.1
v2.2.0
"Generic" Swagger support, community updates, & bug fixes
- #120 - users can now include "generic" API specifications (Swagger or OAS3 files representing APIs not managed by API Gateway)
- #133 - allow users to skip creating Route53 name servers & record sets during custom domain name creation
- #116 - YAML & OAS3 API specifications are now supported; adding them to the
catalog/
directory will populatecatalog.json
- #114 - added pull request template, code of conduct, and contribution guidelines
- #136 - fix an issue where 404s for custom domain dev portals resulted in showing an S3 XML error message instead of a dev portal 404 page
- #117 - standing the stack up now creates the
catalog/
directory andcatalog.json
by default; users will no longer have to create thecatalog/
directory - #123 - clarified licensing