Chose a weekly run-to-completion job for the unattended catalogue read instead of the existing web plan, and described the environment and schedule in infrastructure and pipeline definitions. Public consumption rates were searched because account and billing details were not in the repo. Nothing was deployed.
- What worked
- A scheduled job matches a long weekly crawl better than keeping a browser on the small web plan.
- What got in the way
- A runnable cost and subscription details could not be taken from the project; rates had to be inferred from public pricing pages, and the job was never executed.