We are pleased to announce version 0.9.0 of igluctl
Igluctl is a CLI application for common Iglu registry tasks. You can find out more about igluctl on our docs site
igluctl lint validates json schemas.
You can pass a specific schema or a directory containing schemas to
igluctl lint. Sometimes, when you pass a directory containing many schemas there are some schemas with known issues.
There is existing support to skip specific checks. For example you could run:
/path/to/igluctl lint --skip-checks description,rootObject /path/to/schema/registry/schemas
rootObject checks (more info on
--skip-checks here) if you know that those schemas with known linting problems fail those checks. But if you are adding new schemas to the directory, you might want to apply all linting rules to the schemas in your directory, and exclude the schemas with known
linting issues. Now you can. For example, you could run:
/path/to/igluctl lint /path/to/schema/registry/schemas --skip-schemas iglu:com.acme/click/jsonschema/1-0-1,iglu:com.acme/scroll/jsonschema/1-0-1
to lint all the schemas in
You can use
igluctl static s3cp to send json schema to an s3 bucket. Whenever you upload objects to S3, there is associated metadata.
Previously, when you would run for example:
/path/to/igluctl static s3cp /path/to/schema/registry/schemas my-s3-bucket-name
The schemas in
/path/to/schema/registry/schemas would happily make their way to
my-s3-bucket-name, but the associated metadata for each schema would say
Now, as of igluctl 0.9.0, the metadata for each schema would say
Content-Type will say
application/json; charset=UTF-8 which is preferable because
igluctl static s3cp is for sending json schema.
More details re: dependency bumps and tidying up unused options in the release notes here