5656d7388c
I noticed we had two mechanisms for unit test override. One that dropped a sentinel into the env var, and another with a struct member on TestCase. This consolidates the two, using the cleaner struct member internal mechanism and the nicer `resource.UnitTest()` entry point. |
||
|---|---|---|
| .. | ||
| test-fixtures | ||
| data_source_state.go | ||
| data_source_state_test.go | ||
| flatten.go | ||
| provider.go | ||
| provider_test.go | ||