integrations / integrations/terraform-provider-github

Proposal: Separate `resource_github_organization_custom_properties` into separate resources per `value_type`

Open
#3,191 5 comments 1 reaction 0 assignees View on GitHub
r/organization_custom_properties 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 schema doesn't currently map properly to the different `value_type`s and their possibilities (for example: we can't set default values that are arrays https://github.com/integrations/terraform-provider-github/issues/2806)

Instead of making the single resource very complex with conditional logic and some weird schema fields, I'd propose we create separate Org Custom Property resource for each `value_type`

### SDK Version

_No response_

### API Version

_No response_

### Relevant log output

```shell

```

### Code of Conduct

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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.