Nexus Repository Helm Format

Developing
- Requirements
- Building
Using Helm with Nexus Repository Manger 3
Installing the plugin
The Fine Print
Getting Help

Developing

Requirements

Apache Maven 3.3.3+
Java 8
Network access to https://repository.sonatype.org/content/groups/sonatype-public-grid

Also, there is a good amount of information available at Bundle Development

Building

To build the project and generate the bundle use Maven

mvn clean package

If everything checks out, the bundle for Helm should be available in the target folder.

In the examples below, substitute 0.0.12 with the current version of the helm format plugin.

Build with Docker

docker build -t nexus-repository-helm:0.0.12 .

Run as a Docker container

docker run -d -p 8081:8081 --name nexus nexus-repository-helm:0.0.12

For further information like how to persist volumes check out the GitHub repo for our official image.

The application will now be available from your browser at http://localhost:8081

As of Nexus Repository Manager Version 3.17, the default admin password is randomly generated. If running in a Docker container, you will need to view the generated password file (/nexus-data/admin.password) in order to login to Nexus. The command below will open a bash shell in the container named nexus:
```
docker exec -it nexus /bin/bash
$ cat /nexus-data/admin.password 
```
Once logged into the application UI as admin using the generated password, you may also want to turn on "Enable anonymous access" when prompted by the setup wizard.

Using Helm With Nexus Repository Manager 3

We have detailed instructions on how to get started here!

Compatibility with Nexus Repository Manager 3 Versions

The table below outlines what version of Nexus Repository the plugin was built against

Plugin Version	Nexus Repository Version
v0.0.6	3.13.0-01
v0.0.7	3.14.0-04
v0.0.8	3.15.2-01
v0.0.9	3.16.2-01
v0.0.10	3.17.0-01
v0.0.11	3.18.0-01
v0.0.12	3.18.0-01
v0.0.13	3.18.0-01

If a new version of Nexus Repository is released and the plugin needs changes, a new release will be made, and this table will be updated to indicate which version of Nexus Repository it will function against. This is done on a time available basis, as this is community supported. If you see a new version of Nexus Repository, go ahead and update the plugin and send us a PR after testing it out!

All released versions can be found here.

Features Implemented In This Plugin

Feature	Implemented
Proxy	✔️ *
Hosted	✔️ *
Group

* tested primarily against the Google Helm Chart registry, not guaranteed to work on the wide wild world of Helm repositories.

Supported Helm Commands

Proxy

Command	Implemented
`helm repo add`	✔️
`helm install`	✔️

Hosted

TBD

Installing the plugin

There are a range of options for installing the Helm plugin. You'll need to build it first, and then install the plugin with the options shown below:

Temporary Install

Installations done via the Karaf console will be wiped out with every restart of Nexus Repository. This is a good installation path if you are just testing or doing development on the plugin.

Enable Nexus console: edit <nexus_dir>/bin/nexus.vmoptions and change karaf.startLocalConsole to true.

More details here: Bundle Development

Run Nexus' console:

# sudo su - nexus
$ cd <nexus_dir>/bin
$ ./nexus run
> bundle:install file:///tmp/nexus-repository-helm-0.0.12.jar
> bundle:list

(look for org.sonatype.nexus.plugins:nexus-repository-helm ID, should be the last one)

> bundle:start <org.sonatype.nexus.plugins:nexus-repository-helm ID>

(more) Permanent Install

For more permanent installs of the nexus-repository-helm plugin, follow these instructions:

Copy the bundle (nexus-repository-helm-0.0.12.jar) into <nexus_dir>/deploy

This will cause the plugin to be loaded with each restart of Nexus Repository. As well, this folder is monitored by Nexus Repository and the plugin should load within 60 seconds of being copied there if Nexus Repository is running. You will still need to start the bundle using the karaf commands mentioned in the temporary install.

(most) Permanent Install

If you are trying to use the Helm plugin permanently, it likely makes more sense to do the following:

Copy the bundle into <nexus_dir>/system/org/sonatype/nexus/plugins/nexus-repository-helm/0.0.12/nexus-repository-helm-0.0.12.jar

Make the following additions marked with + to <nexus_dir>/system/org/sonatype/nexus/assemblies/nexus-core-feature/3.x.y/nexus-core-feature-3.x.y-features.xml

      <feature prerequisite="false" dependency="false">nexus-repository-rubygems</feature>
+     <feature prerequisite="false" dependency="false">nexus-repository-helm</feature>
      <feature prerequisite="false" dependency="false">nexus-repository-gitlfs</feature>
  </feature>

And

+ <feature name="nexus-repository-helm" description="org.sonatype.nexus.plugins:nexus-repository-helm" version="0.0.12">
+     <details>org.sonatype.nexus.plugins:nexus-repository-helm</details>
+     <bundle>mvn:org.sonatype.nexus.plugins/nexus-repository-helm/0.0.12</bundle>
+ </feature>
 </features>

This will cause the plugin to be loaded and started with each startup of Nexus Repository.

The Fine Print

It is worth noting that this is NOT SUPPORTED by Sonatype, and is a contribution of ours to the open source community (read: you!)

Remember:

Use this contribution at the risk tolerance that you have
Do NOT file Sonatype support tickets related to Helm support in regard to this plugin
DO file issues here on GitHub, so that the community can pitch in

Phew, that was easier than I thought. Last but not least of all:

Have fun creating and using this plugin and the Nexus platform, we are glad to have you here!

Getting help

Looking to contribute to our code but need some help? There's a few ways to get information:

Chat with us on Gitter
Check out the Nexus3 tag on Stack Overflow
Check out the Nexus Repository User List

de-robat/nexus-repository-helm