Provider Ephemeral Resources
by hashicorpf706481af9b8MPL-2.0890 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 days ago
Implement Terraform provider ephemeral resources with the Plugin Framework: the Open/Renew/Close lifecycle, ephemeral schema design, registration via EphemeralResources, renewal for expiring credentials, and how ephemeral values flow into write-only attributes and provider configuration. Use when adding an ephemeral resource, exposing secrets/tokens/certificates that must never persist in state or plan, deciding between an ephemeral resource and a data source, or wiring short-lived credentials from one provider into another.
- f706481af9b8Currentcommit f706481Published Oct 8, 2026
Source and attribution
Source:hashicorp/agent-skillsinplugins/terraform/skills/provider-ephemeral-resourcesat commitf706481
License: MPL-2.0
Content belongs to its original authors. SourceWeft indexes it from a public repository.
More from hashicorp/agent-skills
Terraform Test
hashicorp
Guides writing and running Terraform tests with .tftest.hcl files, run blocks, assertions, mocks and CI integration.
Terraform Style Guide
hashicorp
Generates and reviews Terraform HCL code following HashiCorp's official style conventions and best practices.
Terraform Stacks
hashicorp
Guides writing and validating HashiCorp Terraform Stacks configuration files for multi-environment infrastructure.
Terraform Policy
hashicorp
Writes, tests and converts Terraform Policy files (.policy.hcl, .policytest.hcl) and Sentinel policies.
Refactor Module
hashicorp
Guides refactoring monolithic Terraform configurations into reusable, maintainable modules with migration and tests.
Provider Resources
hashicorp
Implement Terraform Provider resources and data sources using the Plugin Framework: CRUD operations, schema design, plan modifiers and validators, not-found handling, waiters for eventually consistent APIs, import support, resource design principles, and required acceptance test coverage. Use when adding or changing a resource or data source, deciding whether an API concept should be a resource, wiring a resource to the provider's configured client, handling drift or resource-not-found, or reviewing a resource implementation before submission.