[FEAT]: Support for Ephemeral Resources

[evantissot]

Describe the need

Hello!
I'm reaching out to inquire about the potential support for ephemeral resources within the GitHub Terraform provider.
My specific use case involves creating pull requests (PRs) using this provider. I don't really need to store the PR resource in the state? Currently, I have to apply Terraform a second time to remove these resources from the state. Ephemeral resources would be a great addition, allowing resources to exist temporarily without being stored persistently.
Is there any plan to support this feature in the future?
Thank you

SDK Version

No response

API Version

No response

Relevant log output

Code of Conduct

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

[twaslowski]

Seconding this. Specifically providing write-only implementations of github_actions_secret and github_dependabot_secret would be incredibly helpful.

[davidjoliver86]

I would love to be able to manage github_repository_deploy_key resources using a write-only argument referencing an ephemeral tls_private_key resource.

[honi]

I would love to be able to manage github_repository_deploy_key resources using a write-only argument referencing an ephemeral tls_private_key resource.

I want the exact same thing.

[yannickvr]

github_repository_file and github_repository_pull_request need this too

[deiga]

Hey there 👋

As this provider is still using terraform-plugin-sdk/v2 we don't have direct access to Ephemeral Resources yet. At some point in the future there are plans for migrating to use terraform-plugin-framework instead, but that timeline is as of yet unknown.

[kokolight]

Hey @deiga , What about adding write only option to make sure the value of the secret is not written into the state?
This way you can leverage tools like sops to store the secret encrypted and use it in the github action secret creation.
You can see in other providers like aws with ssm_parameter as a reference, just need to add *_wo at the end and this way you can keep the current behavior as it is and no need to do any breaking changes.

[deiga]

Hey @deiga , What about adding write only option to make sure the value of the secret is not written into the state?
This way you can leverage tools like sops to store the secret encrypted and use it in the github action secret creation.
You can see in other providers like aws with ssm_parameter as a reference, just need to add *_wo at the end and this way you can keep the current behavior as it is and no need to do any breaking changes.

I think write-only attributes are a good idea! We'd love to see a contribution for this ☺️