scottmuc / infrastructure

Documentation / Automation for personal third-party infrastructure
The Unlicense
11 stars 2 forks source link

Rebuild WSL - First attempt and repaving WSL #37

Closed scottmuc closed 2 years ago

scottmuc commented 2 years ago

Yay for Repaving!

As much as possible is documented inline in this issue template. In case of problems you may find help by viewing all the previous repave issues. Have fun!

Steps

scottmuc commented 2 years ago

To destroy the instance, wsl --unregister Ubuntu-20.04

Recreated the env via wsl --install -d Ubuntu-20.04.

Created a user wsl for this purpose.

Then...

cd ~
mkdir workspace
cd workspace
git clone https://github.com/scottmuc/infrastructure.git
cd infrastructure/homedirs/wsl
scottmuc commented 2 years ago

First hiccup was installing terraform. Need to setup the apt repositories. Also... revisiting how I install ansible. Maybe I'll just pip install it.

scottmuc commented 2 years ago

The new op CLI doesn't like me having logins with @ in them:

~/workspace/infrastructure/homedirs ? gpg_op restore -e "scott@scottmuc.com"
[ERROR] 2022/04/18 18:53:14 could not read secret op://Automation/gpg.scott@scottmuc.com/base64.secret.key: invalid secret reference 'op://Automation/gpg.scott@scottmuc.com/base64.secret.key': invalid character in secret reference: `@`
[ERROR] 2022/04/18 18:53:14 could not read secret op://Automation/gpg.scott@scottmuc.com/base64.ownertrust: invalid secret reference 'op://Automation/gpg.scott@scottmuc.com/base64.ownertrust': invalid character in secret reference: `@`
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
scottmuc commented 2 years ago

Ansible worked after running ansible-galaxy collection install ansible.posix which I need for the USB drive mount. I'll put it in the coalesce script, but I think in the future, I want to bring things out of that script and closer to where they are actually needed.

scottmuc commented 2 years ago

This went smoother than expected. I'll look at fleshing out the checklist more fully next time now that I've capture a lot of the missing elements. I like the idea having less details in the checklist and have the checklist items point to a README section for those particular instructions (e.g.: the DNS or ansible ones)... though this goes against my primary motivation to have everything near the checklist.

The pendulum is always swinging...