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

[deiga]

Describe the need

The schema doesn't currently map properly to the different value_types and their possibilities (for example: we can't set default values that are arrays #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

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labeled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

[stevehipwell]

I'm not sure this is worth the effort given that we can use a string array. When we can use the framework we can use dynamic types, so wouldn't want separate resources.

[nicksilver-map]

I'm not sure this is worth the effort given that we can use a string array. When we can use the framework we can use dynamic types, so wouldn't want separate resources.

Can you clarify if that is a workaround to issue 2806?

[stevehipwell]

@nicksilver-map #2806 can be resolved now that the SDK supports managing multi-select defaults. Off the top of my head we'd need to either wait for a major version to make default a set (with validation) instead of a single string, or we could add a new defaults to support multiple values.

[mkushakov]

@stevehipwell this PR should address this issue #3234 any chances you can review it?