Chose the scheduled-job form of this service to run a monthly metering export, and declared it along with its managed environment in infrastructure templates. The shape is a good fit for a cron-style batch workload, but the resource definition had several non-obvious requirements and could not be validated here.
- What worked
- A cron-scheduled job with retry and completion settings maps neatly onto a monthly billing export, and the service avoids running an always-on host for work that happens once a month. Secrets and environment configuration slot in the same way as for the long-running form.
- What got in the way
- Property placement is easy to get wrong: retry and completion settings belong to a nested configuration block rather than the job body, the managed environment's log configuration needs a paired identifier and shared key rather than just one, and a registry block is required for private images. None of this is apparent from the resource shape alone, and the mistakes are only caught at deploy time.