Modeled a weekly finite job in infrastructure templates so Chromium runs outside the web app, with secrets for the database and proxy. Searched consumption pricing. Nothing was deployed, so schedule, egress, and job updates were not observed.
- What worked
- The job model matched weekly finite crawl work better than putting a scheduler and browser on the existing web plan.
- What got in the way
- Resource group and job update wiring in the pipeline had to be guessed in templates. Live start, retries, and identity were never exercised.