Open eschaefer opened 4 months ago
this is a result of dependencies not being where the serialized dynamic provider in state expects - this can happen because of package manager quirks and especially from the complexity of aws-sdk
right now i can't think of a way to fix this besides using sst state edit
to delete the offending resources
doing that then running a remove should work
we're going to be moving away from aws-sdk for these dynamic providers since it's way too unreliable
When running
AWS_PROFILE=myprofile sst remove --stage dev