Skip to content

fix(frontier): default billing refresh intervals to frontier defaults instead of disabling sync#141

Merged
rohilsurana merged 3 commits into
mainfrom
fix/frontier-refresh-interval-defaults
Jul 2, 2026
Merged

fix(frontier): default billing refresh intervals to frontier defaults instead of disabling sync#141
rohilsurana merged 3 commits into
mainfrom
fix/frontier-refresh-interval-defaults

Conversation

@rohilsurana

@rohilsurana rohilsurana commented Jul 2, 2026

Copy link
Copy Markdown
Member

Problem

The frontier chart sets four billing refresh interval env vars to 0 on frontier-app:

FRONTIER_APP_BILLING_REFRESH_INTERVAL_CUSTOMER: 0
FRONTIER_APP_BILLING_REFRESH_INTERVAL_SUBSCRIPTION: 0
FRONTIER_APP_BILLING_REFRESH_INTERVAL_CHECKOUT: 0
FRONTIER_APP_BILLING_REFRESH_INTERVAL_INVOICE: 0

An interval of 0 disables that background sync job entirely. For invoice this also disables monthly credit overdraft invoice generation.

Today these var names are not read by frontier: billing is a top-level config key (not under app), and since frontier v0.100.0 (raystack/frontier#1332) the env prefix is FRONTIER_SERVICE_. So frontier silently runs on its built-in defaults. But the chart's stated default is still "disable all billing sync", and if the env var naming is ever aligned with frontier's config, deployments that do not run the worker would silently stop generating invoices.

Change

  • Change the default values from 0 to frontier's built-in defaults: 1m for customer/subscription/checkout, 5m for invoice, so the chart's stated defaults match frontier's actual behavior.
  • Keep the existing FRONTIER_APP_ prefix for consistency with the rest of the chart's config keys; aligning names with frontier's current env binding can be done separately.
  • Bump chart version to 0.3.2.

helm lint stable/frontier passes (pre-existing warnings about missing subchart deps and icon only).

@coderabbitai

coderabbitai Bot commented Jul 2, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@rohilsurana, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 33 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 41449422-b1e0-405d-ba57-4efaa1a96805

📥 Commits

Reviewing files that changed from the base of the PR and between 5784914 and 85a4789.

📒 Files selected for processing (2)
  • stable/frontier/README.MD
  • stable/frontier/values.yaml
📝 Walkthrough

Walkthrough

This pull request updates the stable/frontier Helm chart by renaming billing refresh interval environment variables from FRONTIER_APP_BILLING_REFRESH_INTERVAL_* (integer, defaulted to 0) to FRONTIER_SERVICE_BILLING_REFRESH_INTERVAL_* (string, minute-based defaults: "1m" for checkout/customer/subscription and "5m" for invoice) in values.yaml, with corresponding documentation updates in README.MD. The chart version in Chart.yaml is incremented from 0.3.1 to 0.3.2.

Compact metadata:

  • Type: Configuration/documentation update
  • Files changed: 3 (Chart.yaml, README.MD, values.yaml)
  • Lines changed: +14/-9

Related issues: None specified

Related PRs: None specified

Suggested labels: helm-chart, configuration, documentation

Suggested reviewers: None specified

Poem:
A rabbit hopped through YAML fields so neat,
Swapped app for service, made the intervals sweet.
From zero to minutes, the billing now ticks,
One-em and five-em, clever little tricks.
Version bumped up, the changelog complete! 🐰

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: switching Frontier billing refresh intervals from disabled to default working values.
Description check ✅ Passed The description is directly related to the chart updates, env var rename, default values, and version bump.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@rohilsurana rohilsurana closed this Jul 2, 2026
@rohilsurana rohilsurana reopened this Jul 2, 2026
@rohilsurana rohilsurana merged commit 1234c91 into main Jul 2, 2026
3 checks passed
@rohilsurana rohilsurana deleted the fix/frontier-refresh-interval-defaults branch July 2, 2026 11:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant