Skip to content
Agent Fleet

v0.12.1

Three fixes found while bringing a real ecs-ec2 deployment up on 0.12.0: a Graviton Control Plane that quietly came up on x86_64, per-member cost figures that never settled on a member account of an AWS organization, and agent memory that could not be imported into a workspace that had just been created.

Fixed

Section titled “Fixed”
  • standup.sh --cp-arch arm64 checked the architecture and then deployed the default one. The flag reached the image compatibility check but never the stack, so a deployment that reported “covers arm64” still ran the Control Plane on x86_64.
  • Cost allocation tags could not be read on a member account of an AWS organization, so per-member cost showed as unavailable and the Control Plane logged an access-denied line on every tick. Whether the split works is now decided from the figures themselves, which is also the more accurate answer: activation takes up to a day to take effect on AWS’s side.
  • Importing agent memory into a freshly created workspace failed at the last step. The preview worked and applying it did not, which is exactly what a new environment does first. The failure message now says what went wrong instead of “import failed”.

Upgrade notes

Section titled “Upgrade notes”

Nothing to do.