Skip to content

CHANGELOG.md

Latest commit

 

History

History
245 lines (149 loc) · 6.06 KB

CHANGELOG.md

File metadata and controls

245 lines (149 loc) · 6.06 KB

Changelog

All notable changes to Cedar CLI tool will be documented in this file. Changes to the Cedar language, which are likely to affect users of the CLI, are documented separately in the primary changelog.

Unreleased

  • Add tpe command to run type-aware partial evaluation under feature flag tpe (#1894)

4.7.0

4.6.1

4.6.0

Added

  • New run-tests command to run policy tests in JSON format (#1641)

4.5.1

4.5.0

4.4.1

4.4.0

Added

  • Added json-to-cedar direction to translate-policy command. (#1510, resolving #461)
  • Added --level option to the validate command, exposing level validation through the CLI. (#1508, resolving #1501)
  • Improved the check-parse command, which now checks the parse of policies, schema, and/or entities (whatever is passed). (#1548)

4.3.3

4.3.2

4.3.1

4.3.0

Added

  • Add schema options schema and schema-format for the partially-authorize command (#1416, resolving #1332)

4.2.2

4.2.1

4.2.0

4.1.0

Fixed

  • The formatter will now consistently add a trailing newline, and checking if a file is formatted with --check will require a trailing newline. (resolving #1217)

Added

  • Add a command language-version to print the Cedar language version (#1219)

4.0.0

Changed

  • The default --schema-format is now cedar for all subcommands that take --schema-format. (#750)
  • The --partial-validate option has been replaced with --validation-mode, taking the values strict, permissive (new) and partial. The latter two are kept behind their respective feature flags. (#915)
  • CLI arguments --policy-format and --schema-format now take options cedar or json, as opposed to human or json. Similarly, --direction takes cedar-to-json or json-to-cedar. (#1114)

3.4.1

  • The translate-schema command will now fail when trying to convert a schema to the Cedar schema format where any namespaced type name collides with an unqualified type. (#1212, resolving #1063) This does not change what schema in either format are accepted by the other commands.

3.4.0

3.3.0

Added

  • translate-policy command that translates a policy set in its Cedar format to the JSON format (except comments). (#987)
  • visualize command that allows entity JSON files to be visualized using the graphviz format. (#960)
  • All commands that read policies in JSON format now accept a policy set in addition to a single policy or a policy template. (#1057)
  • experimental partially-authorize command (#1082)

3.2.4

3.2.1

3.2.0

Added

  • A --write flag for the format subcommand. This flag writes the formatted policy to the file specified by the --policies flag. (#795)
  • A --check flag for the format subcommand. This flag checks if the policy is already formatted and exits with a non-zero status if it is not. (#798, resolving #796)

3.1.3

  • The translate-schema command now produces prettier output.

3.1.2

3.1.1

3.1.0

Now uses Cedar language version 3.1.0.

Added

  • Added support for the human-readable schema format (--schema-format human when a schema is needed). The default schema format is still JSON for backward compatibility.
  • Added command translate-schema that translates a schema in the JSON format to its human-readable format and vice versa (except comments).
  • The -p/--policies flag can now be omitted across all subcommands where it is present. If the flag is omitted, policies will be read from stdin.
  • --policy-format flag to many subcommands, allowing you to pass policies in JSON format. The default remains human format.
  • The validate command now takes a --template-linked / -k optional argument, allowing you to validate template-linked policies.
  • The check-parse command also now takes a --template-linked / -k optional argument, allowing you to check whether a template-linked-policies file parses.
  • The --template-linked / -k argument is now also optional to link (previously required). If not provided, the linked policy will only be shown on stdout; if it is provided, the indicated file will be updated with the new link (as before).
  • The evaluate command now shows source spans on parse errors.

Fixed

  • The link command now accepts templates in the Cedar JSON (EST) syntax.

3.0.1

3.0.0

Now uses Cedar language version 3.0.0.

Added

  • --deny-warnings option to validate command. This option turns non-fatal warnings into errors.
  • Requests are now validated by default if a schema is provided. This can be disabled with --request-validation=false.
  • The -s short form can now be used for --schema across all subcommands.

Changed

  • The -p flag now always refers to --policies (not --principal) across all subcommands, while -l refers to --principal. Relatedly, the --policies long form of the flag is also now accepted across all subcommands.
  • The short form of --template-linked was changed from -t to -k.
  • The format subcommand no longer takes a positional file argument.

2.5.0

2.4.7

2.4.6

2.4.5

2.4.4

2.4.3

Now uses Cedar language version 2.1.3.

2.4.2

Now uses Cedar language version 2.1.2.

2.4.1

2.4.0

Now uses Cedar language version 2.1.1.

Changed

  • Input policies for check-parse command can be read from standard input.

Fixed

  • Duplicate policy ids in @id annotations cause the CLI to exit gracefully instead of panicking.

2.3.3

2.3.2

2.3.1

2.3.0

Now uses Cedar language version 2.1.0.

2.2.0

Changed

  • Update cedar-policy and cedar-policy-core dependencies.

2.1.0

Changed

  • Update cedar-policy and cedar-policy-formater dependencies.

Fixed

  • Resolve warning in Cargo.toml due to having both license and license-file metadata entries.

2.0.3

Fixed

  • Update Cargo.toml metadata to correctly represent this crate as Apache-2.0 licensed.

2.0.2

2.0.1

2.0.0

Initial release of cedar-policy-cli.

Uses Cedar language version 2.0.0.