• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

binbashar / leverage / 43605557141
78%

Build:
DEFAULT BRANCH: master
Ran 14 Nov 2026 02:34PM UTC
Jobs 1
Files 44
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 Nov 2026 02:34PM UTC coverage: 67.689%. Remained the same
43605557141

push

github

web-flow
Enhancement | Modernize the ref-arch integration test (#338)

* Enhancement | Modernize the ref-arch integration test

- Drop the obsolete toolbox-image-tag axis and run on Python 3.9 and 3.13 only.
- Use OpenTofu 1.13.2 through opentofu/setup-opentofu, without its wrapper, and
  `leverage tofu` instead of `leverage terraform`; bump the actions.
- Fail when any `leverage tofu` command fails, and when the post-apply plan is
  not empty; destroy in its own step that always runs once the layer was
  initialized.
- Provision cli-test-layer in the cloned ref arch, which now keeps it
  unprovisioned, so the test creates and destroys real resources again.
- On pull requests, only run it when the cli or the way it is installed
  changed, and never on forks or without AWS credentials.
- Run it in the PyPI release gate too, against the built wheel. The install
  steps move to a composite action shared by both jobs.
- Bump the bats job's tofu to 1.13.2.

Closes #330

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Provision cli-test-layer through its provisioned variable

Pass -var=provisioned=true to the plan, apply and destroy of cli-test-layer
instead of editing locals.tf in the cloned ref arch, now that the layer takes
it as a variable (binbashar/le-tf-infra-aws#1335).

Check the layer is empty in its own step, and destroy only when that check
passed: resources that already exist belong to someone else (e.g. a /tofu
apply test in the ref arch) and must not be destroyed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Serialize the ref-arch round trip across workflow runs

max-parallel only serializes the jobs of one run. Two runs (two pull requests,
or a pull request and a release) could interleave their plan, apply and
destroy on the same layer and fail each other. A shared concurrency group,
without cancelling the run in progress, runs one round trip at a time.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-a... (continued)

588 of 1080 branches covered (54.44%)

Branch coverage included in aggregate %.

2898 of 4070 relevant lines covered (71.2%)

0.71 hits per line

Jobs
ID Job ID Ran Files Coverage
1 43605557141.1 14 Nov 2026 02:34PM UTC 44
67.69
GitHub Action Run
Source Files on build 43605557141
  • Tree
  • List 44
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #43605557141
  • 95105352 on github
  • Prev Build on master (#43602386584)
  • Next Build on master (#43607108426)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc