Release Notes TOC

A-127 release notes

A-127 version 0.11

On Tuesday, January 20, 2015, we released a new version of A-127.

New features

Remote services

Apigee-127 account providers can expose remote services. For instance, the apigee account provider currently exposes a RemoteProxy service. See "Understanding remote services".

New a127 command-line features

• New service commands for creating, listing, and delete remote services.

• New project commands for binding and unbinding remote services to projects.

• New flow for account creation. You are now prompted to create remote services if you wish. currently, the only available service is RemoteProxy.

Note: The apigee-remote-proxy is no longer deployed by default.

See the a127 command-line reference for details.

Latest version of the Swagger Editor

• New "Try this operation" feature lets you execute a request directly from the editor!

Issues Fixed:

• Fixed #273: Use headers from getHeaders to include all headers.and Content-Length
• Fixed #270: Fix Windows start-up issue
• Fixed #271: Add 'About Swagger Editor' menu option and modal and some UI modification
• Fixed #277: Support printing generated document
• Fixed #28: Send correct data in POST requests (try operations)
• Fixed #289: Update versions of YAML processing libraries
• Fixed #291: Clone deep path array of error object before sending it to AST Manager

Recent swagger-tools releases

A-127 depends on swagger-tools. Here are release notes for recent swagger-tools releases that are supported by a127 0.11

#####v0.7.4

• Attached the original data sent to res.end to response validation errors (Issue #110)
• Response validation for Swagger 2.0 now takes the default response into account when validating (Issue #99)
• Removed requirement for servers to wire up body/query string parsers (We default to body-parser and qs respectively.) (Issue #70)

v0.7.3

• Updated the version of Z-Schema being used to fix some browser issues (Issue #94)
• Updated to build/test the browser using gulp gulp test (Issue #96)
• Specification APIs for Swagger 2.0 now do a full validation prior to performing the business logic behidn the API (Issue #97)
• Fixed Quick Start documentation example (Issue 101)
• Fixed a bug in the CLI where local YAML files were not processed properly (Issue #104)
• Fixed a bug where erroneous validation errors were thrown for valid files due to paths with path paramters and vendor extensions (Issue #103)

v0.7.2

(Contained only upstream release changes)

v0.7.1

• Added API/CLI for Swagger 1.2 to 2.0 conversion (Issue #41)
• Fix browser build (Issue #90)
• Properly support Swagger 2.0 form parameters (Issue #88)
• Support validating responses (Issue #25)

v0.7.0

(Contains breaking changes)

• Add an API (Specification#resolve) to get all of or part of a Swagger document as fully resolved (Issue #63)
• All Specification APIs now require an error-first callback as the last argument
• Fix support for header parameters where case caused an issue (Issue #82)
• Make sure tests that were async were written properly (Issue #65)
• Middleware now requires you to use the initializeMiddleware function during server initialization to validate your Swagger document(s) and return the appropriate middlewares (Issue #77)
• Refactor to support upstream path-level authorizations in Swagger 1.2 (Issue #27)
• Support path parameters that are not path segments (Issue #72)
• Support references throughout the Swagger 2.0 document (Issues: #38, #55, #68, #73, #79)
• Support remote reference (Issue #54)
• Support Swagger 2.0 security (Issue #69)
• Support validating remote files from the CLI (Issue #74)
• Support validating YAML files from the CLI (Issue #75)
• Switched from jjv+jjve for JSON Schema validation to ZSchema
• Validate situation in Swagger 1.2 where the model id and the model's id field are not the same (Issue #71)
• When printing out validation errors/warnings, support inner errors/warnings (Issue #85)
• Various minor bug fixes that did not result in issues
• Various documentation/example fixes to support the changes above

Getting help

If you have questions about A127, you can ask them directly on the [Apigee-127 Community Forum]. Individual GitHub projects within A-127 include issue tracking. See the A-127 help page for details.