PlanResourceChange issue with Create timeout overrides #2386
Assignees
Labels
Comments
6 tasks
VenelinMartinov
changed the title
VenelinMartinov
added a commit
that referenced
this issue
Sep 4, 2024
This adds cross tests for custom timeouts, comparing our handling of custom timeouts with terraform's. To do that we've exposed the `plan` error in tfcheck. Looks like the TF rules are the following: - If the schema specifies a timeout for the operation, then the user is allowed to override that. - If the schema does not specify a timeout, then the resource is said not to support timeouts. That makes it a runtime error if the user then tries to customise the timeout on the resource. That makes sense conceptually, as not all resources would be implemented in a way which supports timeouts. Related to #2386
|
This issue has been addressed in PR #2390 and shipped in release v3.90.0. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Under PlanResourceChange it looks like Create timeout overrides are not respected.
Example
https://github.com/pulumi/pulumi-terraform-bridge/actions/runs/10683196988/job/29610712942?pr=2380
The test TestCustomTimeouts started failing after enabling PRC by default in the bridge.
Output of
pulumi about.
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: