hyperbo.la :: lifestream
permalink

I've now over-engineered an iTunes library integrity checker by turning a script into a module #win

permalink

Just accidentally truncated my .bash_history. Restored from backup but the latest was 55 days ago. #fail

permalink

I had a #patch accepted to an Ansible role I use in my Vagrant environment https://github.com/mprahl/ansible-role-lets-encrypt-route-53/pull/14

permalink

I promised a postmortem: https://hyperbo.la/w/secrets-in-parameter-store-postmortem/

permalink

I was hard down for ~5min last night while rolling out secrets in parameter store. 0.149.0, 0.149.1, 0.149.2, and 0.149.3 were bad releases #fail. 0.149.4 is stable: https://github.com/hyperbola/hyperbola/compare/v0.148.0...v0.149.4. Postmortem pending.

permalink

41-commit weekend 🤩Feel much better about my #webpack , #ansible, and #packer code #win

permalink

The computers did exactly what I told them to do 😕 #fail

permalink

Add in some manual #terraform state edits and deleting things in the #aws console and we're recovered #fail #win

permalink

At least I was able to repro in local #vagrant once I figured out what was going on. #win

permalink

A red herring was adding a call to dd in the cleanup script to zero the free space on the disk. I thought I was somehow filling the disk and not reclaiming space.

permalink

The cleanup script didn't error because my set flags were in the shebang but #packer was invoking the script via bash instead of directly #fail So many yaks.

permalink

This change was introduced in 0.146.0 but did not manifest due to a bug in the cleanup script. I was not passing -y to apt autoremove, which caused the command to abort and end the script with an error. #fail

permalink

Removing just the dev package with #ansible #provisioning had no effect in local env, but combined with the apt purge in the #packer script, uninstalled mysqlclient

permalink

Root cause: My app depends on the python package mysqlclient, which in turn depends on the libmysqlclient system package. I was pulling this in transitively via the dev package required for building.

permalink

Undeployable manifested as healthz returning 502 when adding a new instance to the ALB, marking it as unhealthy and timing out #terraform

permalink

I recently started cleaning up after myself during #provisioning. There are two steps to this: #ansible uninstalls build deps and #packer executes a cleanup script that does an apt purge and autoremove

permalink

Got into an undeployable state due to differences in #provisioning between local and prod environments #fail https://github.com/hyperbola/hyperbola/commit/a914992

permalink

I completed removing build artifacts from source control. Static assets dist and document-root dirs: replaced with running #webpack on host. Third-party #ansible roles: installed from galaxy via #packer and #vagrant at provision time. #win