Integrate Provider Context For Cancelling Requests

[bflad]

Description

In order to properly cancel a Terraform command, we need to reference the provider context to any AWS Go SDK calls and separately any Terraform Plugin SDK retry loops. In Terraform Plugin SDK version 2, the provider context is available via new CRUD function signatures (e.g. CreateContext) (#15090) which will be the starting point for any implementation.

Then when its available to the resources:

• Decide if resource.RetryContext()/WaitForStateContext() should be done as part of this effort or not. Likely separately as it can have its own set of linters.
• Passthrough the provider context.Context to any necessary downstream functions (if not a resource function) that call the AWS Go SDK (and resource.Retry()/StateChangeConf if necessary) -- this also includes generating context-aware keyvaluetags functionality
• If AWS Go SDK is still version 1 for all resources, switch the AWS SDK calls to their WithContext variant and pass through the available resource context.Context to them
• If AWS Go SDK is version 2 for new resources, document the appropriate code steps

[bflad]

Terraform Plugin SDK version 2 introduces CRUD functions (e.g. CreateContext) with the provider context automatically available (#15090) -- will adjust the description of this issue. Depending on the timing of that work and the GA release of AWS Go SDK version 2, the implementation details may change further.

[bflad]

One potential risk to threading the resource context through to all functionality is ensuring that the default resource timeouts (20 minutes) do not interfere with the provider-level max_retries (AWS Go SDK MaxRetries) setting (which defaults to 25 and ~60 minutes). We may not have a choice if it does, but it will be helpful to understand and document the behavior before migrating code to the new goodness, potentially in a major release.

[bflad]

The risk mentioned above is now mitigated with *WithoutTimeout functionality -- the Terraform Plugin SDK v2 function signature migration can be tracked in #15090

Will add internal/keyvaluetags: Generate Context-Aware Functions to the description.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

[ewbankkit]

Closed by #29005.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.