v1.1.3

Release v1.1.3

• feat: ignore errors in matchers and add format byte

The CRD tester now can ignore certain errors. For example:

suite: test ClusterSecretStore
template: tests/crds/clustersecretstore.yml
tests:
  - it: matches ClusterSecretStore correctly
    asserts:
      - matchSnapshot:
          path: tests/__snapshot__
          # We deliberately want to test all the included elements.
          ignoreErrors:
            - "in body should have at most 1 properties"

v1.1.2

Release v1.1.2

• feat: extend the configuration file with the other providers #157

The configuration file has been extended with all the providers.

apiGroups:
  - name: "com.aws.services"
    description: "Resources related to AWS services"
    files: # files and folders can be defined together or on their own
      - sample-crd/infrastructure.cluster.x-k8s.io_awsclusters.yaml
      - sample-crd/delivery.krok.app_krokcommands
  - name: "com.azure.services"
    description: "Resources related to Azure services"
    folders:
      - azure-crds
  - name: "whatever"
    urls:
      - url: https://raw.githubusercontent.com/Skarlso/crd-bootstrap/refs/heads/main/crd-bootstrap/crds/delivery.crd-bootstrap_bootstraps.yaml
    gitUrls:
      - url: [email protected]:Skarlso/crd-bootstrap
      - url: [email protected]:crossplane/crossplane

v1.1.1

Release v1.1.1

• feat: implement discovering CRDs in git repositories directly #155

This feature adds the ability to fetch CRDs through discovery from a git based repository.
It is only supported through the CLI at the moment. For more information, check out the
Pull Request description and the README.

v1.1.0

Release v1.1.0

• feat: add option to generate Details section on the spot #153

This feature introduced an overhaul of the frontend and the Generation
logic. Previously, the required only generation was destructive to the
object. Meaning it actually removed fields that weren't required from the
schema object as it was going through it.

This has been revised. Now, this process is non-destructive. So it can be
called multiple times on the same object. This was introduced so the frontend
now has a switch where it can on-the-fly generate the output based on the
settings provided in the details view.

v1.0.6

Release v1.0.6

• fix: fixing checking additional property when it is not required #149

v1.0.5

Release v1.0.5

• fix: additional properties schema being nil for create html output (#147)

v1.0.4

Release v1.0.4

• add enum values to be displayed properly via #139

v1.0.3

Release v1.0.3

The following features have been completed in this release:

• feat: add config file for optional grouping (#134)
• feat: adding apiVersion and kind value if description is empty (#132)
• feature: inline the CSS instead of using a CDN every time #131
• feat: add x-kubernetes-group-version-kind to the schema #129

v1.0.2

Release v1.0.2

This release adds a small adjustment to the JSON schema generator adding
a small detail about the kind and the group and the version that's being
used by the schema.

v1.0.1

Release v1.0.1

Fix ignoring the random flag for HTML output.