Instead of an external gitops agent, which is using the Registry REST API to perform synchronization, we can reverse the problem and implement the gitops feature as another storage implementation.
The git repository will be checked out locally and managed by Registry, which will monitor the changes and feed them into the internal H2 database. This is similar to the kafkasql storage, but uses a git repo instead of a Kafka topic.
Storing into the git repo using the REST API is out of scope for now. The REST API will be in read-only mode.
As a first PoC, the import/export feature can be used with git directly.
Instead of an external gitops agent, which is using the Registry REST API to perform synchronization, we can reverse the problem and implement the gitops feature as another storage implementation.
The git repository will be checked out locally and managed by Registry, which will monitor the changes and feed them into the internal H2 database. This is similar to the kafkasql storage, but uses a git repo instead of a Kafka topic.
Storing into the git repo using the REST API is out of scope for now. The REST API will be in read-only mode.
As a first PoC, the import/export feature can be used with git directly.
Thread: https://chat.google.com/room/AAAAnK5QyQ0/NzmF_asPdyY