https://aftermarket.dev/tags/afterconfig/ Recent content in afterconfig on Aftermarket.dev Hugo -- gohugo.io en-us Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/afterconfig-released-to-change-vendor-config-files-without-editing-them/ Aftermarket 0.4.0 adds AfterConfig, run as aftermarket config. It’s for the config file a vendor ships with its app, the one you have to change and every upgrade overwrites. The usual fix is to edit the file and keep a note somewhere. Then the upgrade lands, the note gets forgotten, and the app runs on vendor defaults again. Or worse, someone copies the old file back over the new one and wipes out a setting the vendor added on purpose. https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/case-study-getting-through-a-vendor-upgrade-with-afterconfig-guards/ This case uses the examples/vendor-app folder that ships in every download archive, so you can run each step yourself. The commands and output below come from a real run of the downloaded aftermarket 0.4.0. The situation A team runs a vendor’s app. It reads config.json, and each upgrade replaces that file. The team needs seven changes: a longer timeout more workers JSON logs no telemetry their own database password a bigger connection pool a body limit the vendor doesn’t offer yet They keep those changes in overlay. https://aftermarket.dev/how-afterconfig-was-tested-to-never-write-a-vendor-config-file/ Wed, 21 Oct 2026 00:00:00 +0000 https://aftermarket.dev/how-afterconfig-was-tested-to-never-write-a-vendor-config-file/ AfterConfig makes four promises, and the tests go after each one. It never writes the vendor’s file. It never changes what the overlay doesn’t name. A failed apply leaves the old output alone. And it never prints a secret. The vendor’s file The test makes the vendor’s file read-only and runs every command against it. Then it names that file as the output in six ways: directly, through a symbolic link, through a hard link, through a linked folder, as a relative path, and with a .