chore: Clarify vpc-origin timeouts description #173
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Clarified the description of the
vpc_origin_timeoutsvariable to make it clear that the timeouts apply to Terraform operations (create, update, delete) rather than the resource itself.Motivation and Context
The previous description could be interpreted as affecting the runtime behavior of the VPC origin resource.
This update improves clarity by explicitly stating that the timeouts only influence Terraform’s behavior during resource lifecycle operations.
Breaking Changes
None.
This change affects documentation only and does not modify any Terraform logic or resources.
How Has This Been Tested?
examples/*to demonstrate and validate my change(s)examples/*projectspre-commit run -aon my pull request