You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're planning to use the http provider to query a REST Api and receive a Token that we'll use in the provider-configuration of another provider.
Every time the Terraform code is planned or applied, a new Token is created, causing lots of requests to the API-Server, as well as planned changes on every run/plan. Especially during development of a new feature, this can become quite messy.
Proposal
It would be great if one could specify a TTL for the Response, so that the result of the Statefile could be reused as long as it's still valid.
Default should be 0.
How much impact is this issue causing?
Low
Additional Information
A similar request can be found in #335, but the difference is that in my case, the result of a previous run should be used. But maybe the solution to the two issues could be combined.
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Terraform CLI and Provider Versions
Use Cases or Problem Statement
We're planning to use the
http
provider to query a REST Api and receive a Token that we'll use in the provider-configuration of another provider.Every time the Terraform code is planned or applied, a new Token is created, causing lots of requests to the API-Server, as well as planned changes on every run/plan. Especially during development of a new feature, this can become quite messy.
Proposal
It would be great if one could specify a TTL for the Response, so that the result of the Statefile could be reused as long as it's still valid.
Default should be 0.
How much impact is this issue causing?
Low
Additional Information
A similar request can be found in #335, but the difference is that in my case, the result of a previous run should be used. But maybe the solution to the two issues could be combined.
Code of Conduct
The text was updated successfully, but these errors were encountered: