Skip to content

Fix #1333: Add repository_password_wo write-only attribute and mark repository_password as sensitive - #1826

Open
dennismdejong wants to merge 1 commit into
hashicorp:mainfrom
dennismdejong:fix/1333-repo-password-sensitive
Open

Fix #1333: Add repository_password_wo write-only attribute and mark repository_password as sensitive#1826
dennismdejong wants to merge 1 commit into
hashicorp:mainfrom
dennismdejong:fix/1333-repo-password-sensitive

Conversation

@dennismdejong

Copy link
Copy Markdown

Description

This PR addresses issue #1333 by adding a new write-only attribute repository_password_wo that allows users to provide repository passwords without storing them in the Terraform plan/state.

Changes

resource_helm_release.go

  • Added RepositoryPasswordWO field to HelmReleaseModel struct
  • Added repository_password_wo schema attribute with WriteOnly: true
  • In Create: resolves password from repository_password_wo (config) when repository_password (plan) is empty
  • In Update: same resolution logic
  • In chartPathOptions: falls back to repository_password_wo when repository_password is empty

data_helm_template.go

  • Added RepositoryPasswordWO field to HelmTemplateModel struct
  • Added repository_password_wo schema attribute
  • In Read: resolves password from repository_password_wo when repository_password is empty
  • In chartPathOptionsModel: falls back to repository_password_wo when repository_password is empty

@dennismdejong
dennismdejong requested review from a team, iam404 and rigalGit as code owners July 27, 2026 18:10
@dennismdejong
dennismdejong force-pushed the fix/1333-repo-password-sensitive branch from 6f01e17 to 5023f17 Compare July 27, 2026 18:10
@github-actions github-actions Bot added size/S and removed size/M labels Jul 27, 2026
@MGSousa

MGSousa commented Sep 2, 2026

Copy link
Copy Markdown

PR already created here: #1761

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants