When an AMI name collision occurs during image creation, use a safe
replacement strategy:
1. Create temp image with unique name
2. Wait for temp image to be available
3. Copy temp image to final name
4. Wait for final image to be available
5. Only then deregister old and temp images
This ensures CI jobs always have a working AMI available during
the daily image rebuild - the old image is kept until the new
one is fully ready.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
exploratory look into https://github.com/oven-sh/bun/issues/1524
this still leaves that far off from being closed but an important first
step
this is important because this script is used to spawn our base images
for CI and will provide boxes for local testing
not sure how far i'll get but a rough "road to freebsd" map for anyone
reading:
- [x] this
- [ ] ensure `bootstrap.sh` can run successfully
- [ ] ensure WebKit can build from source
- [ ] ensure other dependencies can build from source
- [ ] add freebsd to our WebKit fork releases
- [ ] add freebsd to our Zig fork releases
- [ ] ensure bun can build from source
- [ ] run `[build images]` and add freebsd to CI
- [ ] fix runtime test failures
<img width="2072" height="956" alt="image"
src="https://github.com/user-attachments/assets/ea1acf45-b746-4ffa-8043-be674b87bb60"
/>
