Azure credentials secret uses incorrect Values path

Open Beginner friendly
#882 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
65/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
yaml
Domain
devops

Research direction

Start by reading helm/postgresql-cluster/templates/origin-azure-creds.yaml and helm/postgresql-cluster/templates/recovery-azure-creds.yaml, then compare their .Values paths with the chart's replica configuration. Check the related backup-azure-creds template for naming consistency. Done means Azure replica credentials use the intended values path and the origin/recovery naming is no longer confusing.

Written by the indexing model from the issue text.

Description

bug chart( cluster )

There is a configuration mismatch in the helm template for Azure replica credentials:
File: helm/postgresql-cluster/templates/origin-azure-creds.yaml
Secret data fields read values from: .Values.recovery.azure.* instead of the replica configuration path

File: helm/postgresql-cluster/templates/recovery-azure-creds.yaml
Secret data fields read also from .Values.recovery.azure.*

and one more thing, there are backup-azure-creds and recovery-azure-creds, but then suddenly origin-azure-creds, which is is slightly confusing

Dominant language
Go Template
Stars
622
Forks
264
Avg merge
6d 16h
Merged PRs (30d)
8

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.

More from cloudnative-pg/charts

All issues in cloudnative-pg/charts

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.