deviceinsight / deviceinsight/helm-maven-plugin

Support configuring multiple repositories

Open
#78 0 comments 3 reactions 0 assignees View on GitHub
enhancement
Dominant language
Kotlin
Stars
48
Forks
20
PR merge metrics
No merged PRs in 30d

Description

Currently, there's a somewhat random step in the `PackageMojo` that adds an incubator repository. #77 allows us to disable this step, which was necessary for a CI pipeline that is behind a very restrictive firewall that doesn't allow access to the publicly available incubator repository.

In the long term, it would be way nicer if we would not make any assumptions about incubator or regular repositories. We could just support configuring a list of repositories and their alias, as well as a separate repository for deploying/publishing a chart.

This could look similar to the following lines:

~~~ xml



myChartRepo
https://example.github.io/chart-repo/



https://example.com/helm
PUT

~~~

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the PackageMojo step that adds the incubator repository and the configuration example in this issue. Define how a list of named Helm repositories, optional credentials, and a separate publish repository should be represented and consumed. Done means the plugin makes no assumptions about incubator or regular repositories and supports the requested publishing configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kotlin, kubernetes
Domain
build-system, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.