Skip to content

Latest commit

 

History

History
140 lines (124 loc) · 6.51 KB

DIFF.md

File metadata and controls

140 lines (124 loc) · 6.51 KB
Raw

Diff

The oasdiff diff command displays the diff between OpenAPI specs.
Output is fully detailed, typically in yaml or json but also available in text, markdown and html formats.
This commmand is typically used to generate a structured diff report which can be consumed by other tools but it can also be viewed by humans.

Output Formats

The default diff output format is yaml.
Additional formats can be generated using the --format flag:

  • yaml: includes all diff details
  • json: includes all diff details
  • text: designed to be more user-friendly and provide only the most important parts of the diff (also compatible with markdown)
  • html: designed to be more user-friendly and provide only the most important parts of the diff (see also changelog with html)

Notes:

  • an empty yaml or json result signifies that the diff is empty, or, in other words, there are no changes.
  • the json format excludes the endpoints section to avoid the complex mapping keys problem.

Preventing Changes

A common way to use oasdiff diff is by running it as a step the CI/CD pipeline to detect changes.
In order to prevent changes, oasdiff diff can be configured to return an error if changes are found.
To exit with return code 1 if any changes are found, add the --fail-on-diff flag.

Paths vs. Endpoints

OpenAPI Specification has a hierarchical model of Paths and Operations (HTTP methods).
Oasdiff follows this hierarchy and displays a hierarchical diff with path changes: added, deleted and modified, and within the latter, "modified" section, another set of operation changes: added, deleted and modified. For example:

paths:
    deleted:
        - /register
        - /subscribe
    modified:
        /api/{domain}/{project}/badges/security-score:
            operations:
                modified:
                    GET:

Oasdiff also outputs an alternate simplified diff per "endpoint" which is a combination of Path + Operation, for example:

endpoints:
    deleted:
        - method: POST
          path: /subscribe
        - method: POST
          path: /register
    modified:
        ?   method: GET
            path: /api/{domain}/{project}/badges/security-score
        :   tags:
                deleted:
                    - security

Complex Mapping Keys

The modified endpoints section has two items per key, method and path, this is called a complex mapping key in YAML.
Some YAML libraries don't support complex mapping keys, for exampple:

To overcome this limitation, oasdiff allows you to exclude the endpoints section by adding the following flag: --exclude-elements=endpoints.
When using json output format, oasdiff excludes endpoints automatically.

OpenAPI Extensions

Oasdiff tracks changes to OpenAPI extensions by default. To disable this, see Excluding Specific Kinds of Changes.
The diff format for OpenAPI extensions conforms with JavaScript Object Notation (JSON) Patch, for example:

endpoints:
    modified:
        ?   method: POST
            path: /example/callback
        :   extensions:
                modified:
                    x-amazon-apigateway-integration:
                        - oldValue: "201"
                          value: "200"
                          op: replace
                          from: ""
                          path: /responses/default/statusCode
                        - oldValue: http://api.example.com/v1/example/callback
                          value: http://api.example.com/v1/example/calllllllllback
                          op: replace
                          from: ""
                          path: /uri

Excluding Specific Kinds of Changes

You can use the --exclude-elements flag with to exclude one or more of the following:

  • Use --exclude-elements examples to exclude Examples
  • Use --exclude-elements extensions to exclude Extensions
  • Use --exclude-elements description to exclude description fields
  • Use --exclude-elements title to exclude title fields
  • Use --exclude-elements summary to exclude summary fields
  • Use --exclude-elements endpoints to exclude the endpoints section of the diff

For example, this diff excludes descriptions and examples:

oasdiff diff data/openapi-test1.yaml data/openapi-test3.yaml --exclude-elements description,examples -f text

Additional Options

Usage Examples

Diff as YAML

oasdiff diff data/openapi-test1.yaml data/openapi-test2.yaml

The default diff output format is yaml.
No output means that the diff is empty, or, in other words, there are no changes.

Text/Markdown Diff Report

oasdiff diff data/openapi-test1.yaml data/openapi-test2.yaml -f text

The text diff report provides a simplified and partial view of the changes. It is also compatible with markdown.
To view all diff details, use yaml or json formats.

HTML Diff Report

oasdiff diff data/openapi-test1.yaml data/openapi-test2.yaml -f html

The html diff report provides a simplified and partial view of the changes.
To view all diff details, use yaml or json formats.

Comparing remote files over http/s

oasdiff diff https://raw.githubusercontent.com/Tufin/oasdiff/main/data/openapi-test1.yaml https://raw.githubusercontent.com/Tufin/oasdiff/main/data/openapi-test3.yaml -f text

Diff across multiple specs with globs

oasdiff diff "data/composed/base/*.yaml" "data/composed/revision/*.yaml" -c