I Attempted Terraform Remote and Imploded VS Code - Here’s How I Fixed It
By Morgan Lucas
This is a post intended for this site, as a way to get a feel of using it consistently. Older posts are here.
What is Terraform Remote?
It can store state files of Terraform remotely. It’s used more when there are multiple developers working on one thing, so someone’s state isn’t totally overwritten. Similar to CircleCI or Jenkins.
Why Did I Try It?
Because trying things is fun!
What Was the Initial Result?
The code worked - It was my S3 bucket permissions that were a little off, and did not allow me to place anything in there unless I went into the GUI and did it myself - which is time intensive and defeats the purpose of this project a bit.
So...Where Does the Implosion Come In?
VS Code suddenly had a lot of issues with permissions - It seems to have imploded the executable on my machine. I couldn’t start it, (’The location of this file could not be found’), but it wasn’t in my list of programs to uninstall - It was a ghost program. I could delete the files in theory - My permissions had gone screwy as well, and no amount of adjusting or using 3rd party, but Microsoft Approved tools worked. (
What were those tools? When I remember I will edit this.)
How It's Fixed
Solved:
I took a break
Ate a snack
Went outside
Showered
Got a new mug in the mail
Went back to Binging and found the following:
So, there are many places where VS Code files hide - Local folder, Roaming folder, Programs Folder - and while some of them can be deleted, not the one that needed to be.
Now, while the program is not in the Program and Features program, VS Code did come with an uninstaller, which does end up working. Shout out to alshafi on StackOverflow who knew the multiple hidey-holes this program has.