Used the existing API service definition to inject billing environment and secrets into the task. No new cluster or service was created, and the task was not run.
- What worked
- Task image options already supported secret-backed environment values, so billing config could follow the same pattern as the rest of the API.
- What got in the way
- Task startup, secret hydration, and network calls from a running task were not observed.
