v0.4.0

uptest now supports a new command to detect and report breaking API schema changes for the CRDs generated using upjet and between the versions declared in the spec.versions of a CustomResourceDefinition. Here's the help documentation from the new tool:

$ uptest crddiff --help
usage: uptest crddiff <command> [<args> ...]

A tool for checking breaking API changes between two CRD OpenAPI v3 schemas. The schemas can come from either two revisions of a CRD, or from the versions declared in a single CRD.

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Subcommands:
  crddiff revision <base> <revision>
    Compare the first schema available in a base CRD against the first schema from a revision CRD

  crddiff self <crd>
    Use OpenAPI v3 schemas from a single CRD


$ uptest crddiff revision --help
usage: uptest crddiff revision <base> <revision>

Compare the first schema available in a base CRD against the first schema from a revision CRD

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Args:
  <base>      The manifest file path of the CRD to be used as the base
  <revision>  The manifest file path of the CRD to be used as a revision to the base


$ uptest crddiff self --help
usage: uptest crddiff self <crd>

Use OpenAPI v3 schemas from a single CRD

Flags:
  --help  Show context-sensitive help (also try --help-long and --help-man).

Args:
  <crd>  The manifest file path of the CRD whose versions are to be checked for breaking changes

What's Changed

• Mark UPTEST_DATASOURCE as optional in e2e workflow by @turkenh in #45
• Contributors can also trigger e2e by @turkenh in #47
• Minor fixes in uptest integration guide. by @turkenh in #49
• Add crddiff: A CRD breaking schema changes detection & reporting tool by @ulucinar in #48

New Contributors

• @ulucinar made their first contribution in #48

Full Changelog: v0.3.0...v0.4.0