A plugin to drone plugin to package and publish helm charts.

Usage

The following settings changes this plugin's behavior.

• param1 (optional) does something.
• param2 (optional) does something different.

Below is an example .drone.yml that uses this plugin.

kind: pipeline
name: default

steps:
  - name: run harnesscommunity/drone-helm-chart-container-registry plugin
    image: harnesscommunity/drone-helm-chart-container-registry
    pull: if-not-exists
    settings:
      param1: foo
      param2: bar

Building

Build the plugin binary:

scripts/build.sh

Build the plugin image:

docker build -t harnesscommunity/drone-helm-chart-container-registry -f docker/Dockerfile .

Testing

Execute the plugin from your current working directory:

docker run --rm -e PLUGIN_PARAM1=foo -e PLUGIN_PARAM2=bar \
  -e DRONE_COMMIT_SHA=8f51ad7884c5eb69c11d260a31da7a745e6b78e2 \
  -e DRONE_COMMIT_BRANCH=master \
  -e DRONE_BUILD_NUMBER=43 \
  -e DRONE_BUILD_STATUS=success \
  -w /drone/src \
  -v $(pwd):/drone/src \
  harnesscommunity/drone-helm-chart-container-registry

"font-size: 10px">
string required | | Docker registry where the packaged chart will be published | | chart_path
string required | | Directory containing the helm chart | | registry_username
string required | | Username to login to the above registry. | | registry_password
string required | | PAT / access token to authenticate | | registry_namespace
string required | | Namespace under which the chart will be published | | gcloud_project_id
string | | Google Artifact Repository project ID |

Notes

If you aim to push Helm Charts to Google Artifact Registry (GAR):

• Set the registry URL to LOCATION-docker.pkg.dev
• use oauth2accesstoken as username and access-token as token. Refer to this documentation for generating an access token.
• use REPO_ID as registry_namespace and PROJECT_ID as gcloud_project_id

In case of Docker Hub:

• Set the registry URL to registry.hub.docker.com

Review the "plugin image" section to identify the available tags for supported architectures, and then use these tags in the Docker Image during the plugin step.

For more details check the examples section.

Plugin Image

The plugin harnesscommunity/drone-helm-chart-container-registry is available for the following architectures:

OS	Tag
linux/amd64	linux-amd64
linux/arm64	linux-arm64
windows/amd64	windows-amd64

Examples

# Plugin YAML
# DockerHub Example
- step:
    type: Plugin
    name: Push Helm Chart to DockerHub
    identifier: helm_chart_docker
    spec:
        connectorRef: harness-docker-connector
        image: harnesscommunity/drone-helm-chart-container-registry:linux-amd64
        settings:
            registry_url: registry.hub.docker.com
            registry_username: <+variable.docker_username>
            registry_password: <+secrets.getValue("docker_pat")>
            chart_path: chart
            registry_namespace: <+variable.namespace>

- step:
    type: Plugin
    name: Push Helm Chart to GAR
    identifier: helm_chart_gar
    spec:
        connectorRef: harness-docker-connector
        image: harnesscommunity/drone-helm-chart-container-registry:linux-amd64
        settings:
            registry_url: LOCATION-docker.pkg.dev
            registry_username: oauth2accesstoken
            registry_password: <+secrets.getValue("access_token")>
            chart_path: chart
            gcloud_project_id: PROJECT_ID
            registry_namespace: REPO_ID

ℹ️ If you notice any issues in this documentation, you can edit this document to improve it.