Connect processes into powerful data pipelines with a simple git-like filesystem interface
CHANGES:
conventional
profile (@avsm).CHANGES:
CHANGES:
CHANGES:
pcdata
function in favour of txt
(@avsm)dune-release
(@avsm)all: update to latest version of alcotest, conduit, session, ocaml-github, ocaml-github-hooks and cohttp (#612, @samoht and @djs55)
github: make User.t
abstract (#594, @samoht)
github: turn Webhook.events
into a promise (#598, @samoht)
github: add a Comment
module to model PR and issue comments (#595, @samoht)
github: change PR.owner
to be of type User.t
(#599, @samoht)
github-bridge: add the ability to sync PR's coments (#595, @samoht)
go-client: handle large values when reading / writing in 9db (#292, @simonferquel)
go-client: fix the handling of defaults over upgrade (#605, @djs55)
go-client: improve transaction API (#606, @djs55)
The main change in this release is the addition of datakit-client-git
which implements the DataKit API on top of a normal Git repository. This
means that the deployment of DataKit tools is now much simpler as they do
not need a running DataKit server anymore. The client and server packages
have been renamed to make the use of 9p more explicit. Support for more
transport is planned, including gRPC and Cap-n-proto.
Go bindings
List
to list files in snapshots (#578, @ebriney)datakit-server, datakit-client
client/server: split the libraires between core API and 9p transport.
There is now:
datakit-client
: signature for client API + Path librarydatakit-server
: implementation of the VFS on top of Irmindatakit-client-9p
: implementation of the API using 9p as transportdatakit-server-9p
: expose the Irmin VFS as the Datakit API; server-side
implementation of the API using 9p as transportThe tests are split as well, so all the client/server tests can be re-used with a different transport mechanism. (#551, @samoht)
client: add a top-level Datakit_client
module namespace: Datakit_S.CLIENT
becomes Datakit_client.S
and Datakit_path
becomes Datakit_client.Path
(#558, @samoht)
client: remove rename
API calls (#563, @samoht)
datakit-client-9p
datakit-client-9p
is now the new name for the previously named
datakit-client
. That package contains the 9p client bindings to the DataKit
API. More clients to come.
DK.commit
now fails if the commit does not exists (instead of
failing later when the commit is used) (#565, @samoht)datakit-client-git
datakit
Datakit
namespace. Expose
Datakit.Blob
, Datakit.Branch
, Datakit.Hash,
Datakit.Metadata
,
Datakit.Path
forming the base types for DataKit stores. Also expose
Datakit.Make
(and Datakit.Make_git
) to build a DataKit store from an
Irmin
store (or from a Irmin_git
store). Finally, rename the functor
to expose a DataKit store into a virtual file-system into Datakit.VFS
(#583, @samoht)datakit-github
datakit-github-bridge
github bridge: look at the GH token in various places (#577, @samoht)
github bridge: add the ability to monitor default repositories using the CLI (#577, @samoht)
github bridge: allow to use git://<path>
urls to "connect" to a local Git
repo instead of a 9p DataKit server (#577, @samoht). For instance:
$ datakit-bridge-github -r samoht/test -d git:///tmp/foo --resync 60
will download all the issues and PR into a Git repository /tmp/foo
and will
keep it up-to-date when changes occur either on GitHub (with a full resync
every 60s) or locally by commiting updates in the /tmp/foo
Git repository.
datakit-ci
DataKit has a new home: the Moby Project!
all
docker run datakit/db
to run the database (see README.md)Datakit_conduit
were depending on datakit-server and it was
not clear which version it was linked with (#532, @samoht)datakit-ci
datakit
datakit-github
datakit-bridge-github
/run/secrets/github-jar
(#519, @talex5)datakit-bridge-local-git
datakit-local-git (new)
Normally, we use datakit-github to monitor the state of a remote repository on GitHub and use that as the input to the CI. When getting started with DataKitCI it is more convenient to be able to monitor a local Git repository.
datakit-bridge-github (new)
datakit-github
package into 2: datakit-github
(see next section) and datakit-bridge-github
which match
datakit-bridge-local-git
(#480, @samoht)datakit-github
Datakit_github
, an abstract
representation of the GitHub types and API (#480, @samoht)datakit-ci
datakit-gitub
to manipulate GitHub metadaa.
This is a major breaking API change (#384, @samoht)Target.v
(#430, @avsm)datakit-client