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

binbashar / leverage / 38777620395
66%

Build:
DEFAULT BRANCH: master
Ran 15 Oct 2026 05:29PM 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

15 Oct 2026 05:28PM UTC coverage: 66.038% (+0.7%) from 65.343%
38777620395

push

github

web-flow
Fix | Credentials configure fails when run after project init (#327)

* Fix | Skip PathsHandler for credentials configure during project bootstrap

leverage credentials configure crashed with "Project name has not been
set" when run right after `leverage project init` and before `leverage
project create`, since only project.yaml exists at that point (neither
build.env nor config/common.tfvars do yet) and PathsHandler can't
resolve a project name from either.

leverage project init/create already skip PathsHandler unconditionally
and need no change. For credentials configure, the top-level group
callback now skips PathsHandler only in that specific corner case, and
the credentials group callback (which already had a half-implemented
branch for this exact scenario) writes build.env from project.yaml's
short_name and builds real, project-scoped paths itself, so AWS
credentials still land in ~/.aws/<project>/ instead of falling back to
the global default location.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

* Fix | Stop AWS CLI probes from crashing credentials configure

`leverage credentials configure --type BOOTSTRAP` crashed with
"Command execution failed: The config profile (...) could not be
found" on a first-ever run, because `_profile_is_configured` calls
`Runner.exec(...)` without `raises=False`. `Runner.exec` defaults to
raising an ExitError on any nonzero exit code, so the intended
"probe, then report" logic (`return not exit_code`) never runs when
the profile has never been configured (exit 255) - it aborts the
whole command instead.

This is a regression from the Docker-removal refactor (#316), which
replaced the old non-raising `_exec` with the new `Runner`/`Runner.exec`
(raises by default) without updating call sites written for the old
contract. Six more `awscli.exec(...)` calls in credentials.py had the
identical shape; `_credentials_are_valid` and `_get_organization_accounts`
had real dead graceful-fallback logic, while `_ge... (continued)

532 of 1040 branches covered (51.15%)

Branch coverage included in aggregate %.

30 of 33 new or added lines in 4 files covered. (90.91%)

93 existing lines in 6 files now uncovered.

2828 of 4048 relevant lines covered (69.86%)

0.7 hits per line

Uncovered Changes

Lines Coverage ∆ File
2
78.49
1.09% leverage/path.py
1
84.62
-4.27% leverage/leverage.py

Coverage Regressions

Lines Coverage ∆ File
77
62.74
3.65% modules/credentials.py
12
78.49
1.09% path.py
1
59.29
-0.32% leverage/modules/auth.py
1
62.74
3.65% leverage/modules/credentials.py
1
84.62
-4.27% leverage.py
1
59.29
-0.32% modules/auth.py
Jobs
ID Job ID Ran Files Coverage
1 38777620395.1 15 Oct 2026 05:29PM UTC 44
66.04
GitHub Action Run
Source Files on build 38777620395
  • Tree
  • List 44
  • Changed 9
  • Source Changed 4
  • Coverage Changed 8
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #38777620395
  • 79fb9d98 on github
  • Prev Build on master (#35021487384)
  • Next Build on master (#38777802466)
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