integrations / integrations/terraform-provider-github

[FEAT]: support write-only secrets attributes for webhook resources

Open
#3,628 4 comments 0 reactions 0 assignees View on GitHub
Status: Triage Type: Feature
Dominant language
Go
Stars
1.2k
Forks
1k
Avg merge
1d 14h
Merged PRs (30d)
8

Description

### Describe the need

The webhook resources (`github_repository_webhook` and `github_organization_webhook`) have a `secret` attribute which is not write-only, and thus the secret is persisted in Terraform state.

A better pattern used in other Terraform providers is to support write-only attributes `secret_wo` and `secret_wo_version` so that the secrets can be sourced from ephemeral resources and not persisted to the Terraform state nor included in a plan.

### GitHub Installation Type

- [ ] GitHub.com (Free, Pro, or Team)
- [ ] GitHub Enterprise Server (on-premises)
- [ ] GitHub Enterprise Cloud with Personal Accounts (github.com)
- [ ] GitHub Enterprise Cloud with Managed Users/EMU (github.com)
- [ ] GitHub Enterprise Cloud with Data Residency (*.ghe.com)
- [ ] I don't know

### Relevant log output

```shell

```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Locate the implementations and tests for the github_repository_webhook and github_organization_webhook resources, then review how other Terraform providers in this repository define write-only attributes. Done means both resources support secret_wo and secret_wo_version while keeping secrets out of Terraform state and plans.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, terraform
Domain
devops, infrastructure
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.