v1.7.0

Discover the new features, logic changes, bug fixes, breaking changes, and known issues and limitations in Piiano Vault release v1.7.0.

New features

• Vault now supports export and import of data and configuration. This change includes the following:
  • New PVAULT_KMS_EXPORT_URI and PVAULT_KMS_EXPORT_SEED environment variables to configure the KMS used for encryption of the exported data.
  • New export query param added to the List objects API to return encrypted objects.
  • New import query param added to Add object, Add objects (bulk), Update object, and Update objects (bulk) APIs to enable importing of built-in fields.
  • New export_key query param added to Add object, Add objects (bulk), Update object, and Update objects (bulk) APIs to enable importing of encrypted objects created by the export process.
  • New export and import commands added to the CLI to enable exporting and importing of data and configuration.
• Get KMS Status API updated to include the status of the export KMS and enhanced to include status of all KMSs.
• New Get object count API added that provides the number of objects in a collection.
• Added 410 (Gone) to permitted response status codes from all APIs.

Bug fixes

• Fix a bug where a failure to get a token's metadata resulted in a 500 error instead of a 404 error.
• Fix a bug where a query by a timestamp field didn't work correctly.
• Fix a bug where using an invalid UUID for an ID path parameter sometimes resulted in a 500 error instead of a 400 error.
• Fix a bug where the CLI iam resource-view command wasn't describing well resources on types.
• Fix a bug where collection names with mixed case caused an error with the encryption APIs.

Breaking changes

• The --create-testing-conf (-t) flag used when running the Vault in a binary mode was changed to --create-conf (-c).
• You now cannot set is_index nor is_unique for properties of types LONG_TEXT, JSON, and BLOB, and custom types that are based on these types.
• The value length of a property with the type ADDRESS or a custom type based on ADDRESS is now limited to 1024 characters (previously, it was unlimited).
• The value length of a property with the type URL or a custom type based on URL is now limited to 2048 characters (previously, it was unlimited).
• Setting PVAULT_DB_MAX_STRING_LENGTH to a value greater than 2048 prevents setting is_index and is_unique for properties whose type is STRING, NAME, GENDER, or TENANT_ID, or custom types that are based on these types.
• All APIs are now strictly require a valid UTF-8 encoding input and return a 400 error if the input is not valid UTF-8.