In my previous post, I introduced the overall architecture of Harbor registry. Many users start to integrate the open source private registry Harbor into their own container solution. For example, a startup called Dataman has embedded Harbor into their offering of a CaaS(Container as a Service) solution. Harbor provides a very useful API for the interoperability of other systems. The API specification is defined and documented in the most popular form: Swagger.
The recent blog post Working with Harbor Registry REST API via Swagger described how to leverage Swagger to test the REST API of Harbor registry server. By using Swagger, you can write your own code to fulfill functionalities such as setting permission of images and getting meta data of images and image synchronization between registry instances.
If you are an advanced user or developer of using an enterprise private Docker registry, you should definitely look into Harbor Registry for extending your use cases.