Skip to content

Conversation

@james00012
Copy link
Contributor

@james00012 james00012 commented Dec 3, 2025

Summary

AWS SDK waiters had hardcoded timeout values that ignored the --timeout flag. This PR sets a default timeout in PrepareContext and updates all resources with deletion waiters to use it.

Test plan

  • Build passes
  • Manual test with --timeout flag

Fixes #964

@james00012 james00012 requested a review from denis256 as a code owner December 3, 2025 16:27
@james00012 james00012 force-pushed the fix/rds-deletion-timeout-964 branch 2 times, most recently from 61787b8 to 9658dc2 Compare December 3, 2025 16:46
@james00012 james00012 changed the title fix: respect --timeout flag for RDS instance and cluster deletion fix: respect --timeout flag for AWS resource deletion waiters Dec 3, 2025
@james00012 james00012 force-pushed the fix/rds-deletion-timeout-964 branch from 9658dc2 to a552b2b Compare December 3, 2025 16:48
@james00012 james00012 marked this pull request as draft December 3, 2025 17:13
@james00012 james00012 force-pushed the fix/rds-deletion-timeout-964 branch from 521c5c8 to 6c3fcfd Compare December 4, 2025 22:29
@james00012 james00012 marked this pull request as ready for review December 4, 2025 22:37
AWS SDK waiters had hardcoded timeout values that ignored the user-specified
--timeout flag. This adds a DefaultWaitTimeout constant (5 minutes) in
base_resource.go and sets br.Timeout in PrepareContext. All resources with
deletion waiters now use .Timeout instead of hardcoded values.

Fixes #964
@james00012 james00012 force-pushed the fix/rds-deletion-timeout-964 branch from 6c3fcfd to ba4a484 Compare December 6, 2025 00:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Timeout doesn't work for rds instance on v0.45.0

3 participants