matthewcummings

FWIW, it was not a simple path/import replacement across all the .go files, I started down that path and hit nested import issues with the code in `/internal`.

Hmm. . . @AniketKariya that didn't work for me.

I have a use case where destroys should only succeed/be allowed if the resource specifies `force_destroy = true`. It looks like it won't work as is: https://github.com/hashicorp/terraform-plugin-sdk/blob/main/helper/resource/testing_new.go#L24

Hasn't been merged yet but I have a PR to handle this in a way similar to `ExpectError`: https://github.com/hashicorp/terraform-plugin-sdk/pull/976

@bflad that makes perfect sense, nonetheless it's perfectly normal for a provider to fail when deleting resources, intentionally, for any number of reasons. I spent some time looking into this...

Hi @detro yes, I have tried that. It doesn't work, when the post test destroy runs, if there's an error, there's no current way to handle it, see https://github.com/hashicorp/terraform-plugin-sdk/blob/main/helper/resource/testing_new.go#L32

@detro any update on this?

@detro checking again. . . any updates here?

I saw those, I ended up just using the AWS SDK directly. I couldn't figure out how to query based on a partition key and a range key together.

Agreed @connor11528, some indication of remote options would be great. Given that you focus on Bay area companies, my assumption would be that they wouldn't really be "fully" distributed companies...