tf test: parallelize teardown operations

[dsa0x]

Fixes #

Target Release

1.13.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.

[liamcervante]

sorry, this didn't occur to me before. Would it work just to have a test that uses two (or more) separate provider instances so they don't share the mutex under the hood anyway? This would be instead of giving the option to disable the locking.

[dsa0x]

The test runs share the same configuration, and I am not sure how would then differentiate the instance they should use.

[liamcervante]

You can specify the provider for each run block:

provider "test" {
  alias = "one"
}

provider "test" {
  alias = "two"
}

run "one" {
  providers = {
    test = test.one
  }
}

run "two" {
  providers = {
    test = test.two
  }
}

Then the run blocks will use different provider instances, and they should be able to parallelise?

[dsa0x]

Ah, good point. I had forgotten that feature was available in the test framework. That could be a solid approach.

I will check if that alias translates to the test provider somehow. Otherwise, we might still be using the same concrete struct.

[dsa0x]

Closed in favor for https://github.com/hashicorp/terraform/pull/37220/files

[github-actions]

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