Releases: kamu-data/kamu-cli
Releases · kamu-data/kamu-cli
Release v0.223.0
[0.223.0] - 2025-02-13
Added
- Increased test coverage of the code responsible for access checks
Changed
- Restructured responsibilities between core and dataset domains upon key dataset CRUD use cases:
- 8 use cases moved from
core
tokamu-datasets
domain - no longer using outbox for "Renamed" and "DependenciesUpdated" events in datasets,
these became internal aspect insidekamu-datasets
domain - simplified creation and commit result structures as they no longer transport new dependencies
- revised many integration tests:
- flow system no longer uses real datasets
- HTTP and GQL use real accounts and dataset entries
- 8 use cases moved from
- Moved several account-related routines from
AuthenticationService
toAccountService
,
the authentication services has focus only on JWT token and login flows - Upgraded to
datafusion v45
(#1063)
Fixed
- GQL metadata query now correctly returns dataset aliases for
SetTransform
event in multi-tenant mode - Handle panic errors in
kamu inspect lineage -- browse
command - Improved result messages for
kamu system diagnose
command
Release v0.222.0
[0.222.0] - 2025-02-06
Added
- New
AccessTokenLifecycleMessage
outbox message which produced during access token creation
Changed
kamu pull
command now can be called with passing<remote_repo>/<dataset_name>
arg
and pull url will be combined automatically
Release v0.221.1
Private Datasets: process acceptance testing feedback: Vol. 1 (#1054) * TransformInput: after validation, use alias only for error messages * OsoDatasetAuthorizer: be prepared to work with duplicates * Release (patch): 0.221.1
Release v0.221.0
[0.221.0] - 2025-01-29
Added
- GQL suport to query and update email on the currently logged account
- Account registration sends
AccountLifecycleEvent
toOutbox
Changed
- Emails are mandatory for Kamu accounts now:
- predefined users need to specify an email in config
- predefined users are auto-synced at startup in case they existed before
- GitHub users are queried for primary verified email, even if it is not public
- migration code for the database existing users
Release v0.220.0
[0.220.0] - 2025-01-27
Changed
- Private Datasets:
- GQL,
DatasetFlowRunsMut::trigger_flow()
: added check of input datasets for accessibility forExecuteTransform
- GQL,
TransformInput::input_dataset()
: dataset may not be accessible - GQL,
MetadataChainMut::commit_event
: added check of dataset inputs for availability forSetTransform
- HTTP: added access check for the dataset router (
DatasetAuthorizationMiddleware
), affected:POST /:dataset/ingest
GET /:dataset/metadata
GET /:dataset/tail
- HTTP,
GET /datasets/:id
: access check corrected - HTTP: replaced access errors with not found errors
- CLI,
kamu pull
: replaced access errors with not found errors
- GQL,
- Continued work on use cases extracting:
ViewDatasetUseCase
EditDatasetUseCase
GetDatasetDownstreamDependenciesUseCaseImpl
GetDatasetUpstreamDependenciesUseCaseImpl
Release v0.219.2
[0.219.2] - 2025-01-24
Added
- Reusable static database migrators
Release v0.219.1
[0.219.1] - 2029-01-18
Fixed
- Reverted unstable AWS API dependencies
Release v0.219.0
[0.219.0] - 2029-01-17
Changed
- Massive crates restructuring around Open Data Fabric code:
src/odf
concentrates large number of related crates now, preparing for future separation in different Git repo- old
opendatafabric
crate becamseodf-metadata
- low-level repository implementations became
odf-storage[-...]
crates - specific storage technologies are gated via features (
lfs
,s3
,http
) DatasetFactory
,Dataset
,DatasetSummary
,DatasetLayout
,BlockRef
,
MetadataChain
and visiting logic now are residents ofodf-dataset
kamu-data-utils
becameodf-data-utils
- multiple utility libraries introduced, shared both via ODF and main Kamu code
(async-utils
,file-utils
,s3-utils
,test-utils
) DatasetRepository
still stays in Kamu core, renamed toDatasetStorageUnit
to better match it's current purpose- import statements pointing at ODF code have been cleaned all over the code base (use
odf
meta-crate only outsidesrc/odf
)
Release v0.218.0
[0.218.0] - 2029-01-17
Changed
- Private Datasets:
- OSO: using user actors / dateset resources that come from the database
- Thus, any access check relies on real entities
- GQL, added
Dataset.visibility()
to get the current visibility value - GQL, added
DatasetMut.setVisibility()
to be able to change the dataset visibility after it has been created - Deletion of previously created (and unused) ReBAC-properties and reindexing
- OSO: updating the schema to use identifiers instead of names
- OSO: added resource storage for access speed
- E2E: Using the correct account in multi-tenant mode
- And also the possibility of set it up
DatasetOwnershipService
: moved to thekamu-dataset
crate area & implemented viaDatasetEntryServiceImpl
- GQL,
DatasetMetadata.currentUpstreamDependencies
: indication if datasets not found/not accessed - GQL,
DatasetMetadata.currentDownstreamDependencies
: exclude datasets that cannot be accessed - E2E: added the ability to create an account using CLI
- OSO: using user actors / dateset resources that come from the database
Release v0.217.3
[0.217.3] - 2025-01-14
Fixed
- Fix crash on resolving dataset by non existing account
- Minor improvements in event sourcing aggregation