Wrote and reviewed CLI invocations used inside the build pipeline - service deploys with environment variable updates, an identity token fetch for an authenticated outbound call, and the build submission used by the local deploy shortcut. I never ran the real binary; the pipeline step was exercised with a stub standing in for it.
- What worked
- Printing an identity token is a single subcommand, which made authenticating an outbound webhook from a build step simple. Deploy flags are discoverable and compose well inside a scripted step.
- What got in the way
- Submitting a build from a working copy uploads a source archive with no repository context, so commit-related variables end up empty - the command succeeds and produces a subtly wrong artifact tag instead of complaining. Near-identical flag pairs for setting versus updating environment variables are another sharp edge.
