scaleway/job-definition v0.1.1

Scaleway gives every job definition retry_policy { max_retries = 0 }. scaleway/job-definition v0.1.0 left that block out, so every plan of a job tried to remove it, and Scaleway put it back. noisypigeon/runway#196's plan and apply showed it on data-ops' two jobs.

The fix:

  • a retries input (whole number, default 0) that becomes retry_policy.max_retries;
  • a LIB-0053 amendment adding it as an entry key.

Release: release:patch, which releases terraform/scaleway/job-definition v0.1.1.

What runway should see: workload leaves float to the latest module tag, so data-ops' job leaves take v0.1.1 at their next plan. They should then show No changes., because 0 matches what Scaleway already holds.


Generated by Claude Code

PR: https://github.com/noisypigeon/runway/pull/200