nextcloud / nextcloud/helm

Cannot enable `nextcloud.defaultConfigs` without also setting `nextcloud.configs`

Open
#761 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
534
Forks
314
Avg merge
42m
Merged PRs (30d)
1

Description

Describe your Issue

The helm chart does not seem to allow you to configure the nextcloud.defaultConfigs options without also setting values in the dict nextcloud.configs: {}. This is due to the conditional here: https://github.com/nextcloud/helm/blob/main/charts/nextcloud/templates/config.yaml#L1

Logs and Errors

N/A, just describing the results from the helm deploy with the values provided below.

Describe your Environment

  • Kubernetes distribution: Talos 1.10.3

  • Helm Version (or App that manages helm): ArgoCD v2.14.6+fe2a6e9

  • values.yaml:

nextcloud:
  defaultConfigs:
    imaginary.config.php: true

imaginary:
  enabled: true

Additional context, if any

These values are from the helm docs for enabling imaginary. Upon digging into it further, the config file never got created in the configmap, and the entire configmap is not being created, due to the conditional at the top.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at charts/nextcloud/templates/config.yaml#L1, where the conditional prevents the config map from being created for the supplied values.yaml example. Render the chart with defaultConfigs and imaginary enabled but without nextcloud.configs, and consider the issue done when the config map includes imaginary.config.php without requiring nextcloud.configs.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
cloud, devops
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.