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

raystack / frontier / 20915422591
38%
main: 38%

Build:
Build:
LAST BUILD BRANCH: fix/env-prefix-collision
DEFAULT BRANCH: main
Ran 12 Jan 2026 10:13AM UTC
Jobs 1
Files 317
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

12 Jan 2026 10:07AM UTC coverage: 37.822% (+0.003%) from 37.819%
20915422591

Pull #1332

github

whoAbhishekSah
fix: change env prefix to avoid K8s service env var collision

Change env prefix from FRONTIER to FRONTIER_SERVICE to prevent collision
with Kubernetes service environment variables.

K8s automatically creates env vars for services (e.g., FRONTIER_APP_PORT
for a service named frontier-app). With Viper's FRONTIER prefix, this
maps to app.port and overrides config file values with invalid URLs like
"tcp://172.20.58.102:80".

With FRONTIER_SERVICE prefix, env vars need to be FRONTIER_SERVICE_APP_PORT
to affect app.port, avoiding the collision.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Pull Request #1332: fix: change env prefix to avoid K8s service env var collision

3 of 3 new or added lines in 1 file covered. (100.0%)

15814 of 41812 relevant lines covered (37.82%)

10.79 hits per line

Jobs
ID Job ID Ran Files Coverage
1 20915422591.1 12 Jan 2026 10:13AM UTC 317
37.82
GitHub Action Run
Source Files on build 20915422591
  • Tree
  • List 317
  • Changed 1
  • Source Changed 0
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #1332
  • PR Base - main (#20841098506)
  • Delete
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc