You also don’t have to use Swagger, that’s just for experimentation and we expect you’ll be scripting your calls. If you want much more control over the results you get, look into the Search endpoint, which allows the same degree of flexibility that you have from our UI-based search feature. fill in the ID of the repository you’re interested in: Just click on the GET action for the assets endpoint: Gimme the GoodsĪ common use case is wanting to list all the assets in a repository. In the NuGet format, which has only NuGet packages (and doesn’t have all those other asset types), each component contains one asset. In the maven2 format, for instance, your jars, poms, src-jars, and wars are all stored as assets, with a component that represents the groupId, artifactId, and version. A component is a logical grouping of files. Each of those formats has a different content model, but internally, we store all of that as components and assets.Īn asset is a binary file of some kind, plus the associated metadata for that file. Nexus Repository 3.x offers format-native support for Maven2, Docker, NuGet, npm, PyPI, RubyGems, Yum proxy, GitLFS, and Bower. You’ll also see our new, beta endpoints for assets and components: In Swagger, you’ll see the familiar Provisioning API endpoints: It’s interactive, so you can fill out parameters, make REST calls and see the results right in your browser. Swagger generates a browser-accessible UI interface from REST endpoints. Many REST calls are made from scripts that drive curl requests, but to make it easy to explore and understand our API, we’ve integrated Swagger. Well, we’ve been busy adding REST endpoints so you can list, search, and download your components as well. You’re probably already aware of our Provisioning API, a REST API you can use to automate the configuration of your Nexus Repository instances. There’s a secret lurking in Nexus Repository Manager, a beta REST API for accessing components.
0 kommentar(er)
