Overview - Console

console

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
180/merge
058aa1a1 feat(QOV-180): chargebee credit card integration (#2143) * chore(deps): bump Qovery API client version Update Qovery API client to support token field in CreditCardRequest for Chargebee tokenization integration. Add NX_PUBLIC_CHARGEBEE_PUBLISHABLE_KEY environment variable. * perf(docker): optimize Dockerfile for faster builds Improvements: - Upgrade from Node 16 to Node 20 (Node 16 is EOL) - Add BuildKit cache mounts for yarn and NX cache - Consolidate ENV declarations to reduce layers - Use specific nginx version (1.25-alpine) instead of latest - Enhance .dockerignore to exclude unnecessary files from build context - Reorder steps to maximize Docker layer caching Expected benefits: - Faster yarn install via cache mount - Faster NX builds via cache mount (incremental builds) - Smaller build context (faster transfer to Docker daemon) - Better layer caching (fewer cache invalidations) * feat(billing): integrate Chargebee.js for secure credit card tokenization This commit integrates Chargebee.js using their React wrapper to handle secure credit card tokenization with PCI-compliant payment processing. Key changes: - Replaced direct Stripe integration with Chargebee.js React wrapper - Implemented CardComponent with individual CardNumber, CardExpiry, and CardCVV fields - Added custom styling to match the existing InputText design system - Implemented global loading state that displays until Chargebee fields are ready - Created chargebee-utils.ts for Chargebee instance management and script loading - Updated tests to mock Chargebee React wrapper components - Fixed linting errors (async promise executor, unnecessary semicolons) Technical implementation: - Uses @chargebee/chargebee-js-react-wrapper for React integration - Chargebee fields render as secure iframes that handle sensitive card data - Token-based approach: card data is tokenized client-side, only tokens sent to backend - Custom CSS styling applied to iframe containers for consistent UI - Loading state tracks both Chargebee instance initialization and field readiness Also includes: - Service alerting creation, edition, and delete flow - Notification channel management - Alert rules and receivers implementation - Various UI improvements and bug fixes * fix: fix linter * fix(billing): remove unnecessary semicolons in chargebee-utils Fixes linting errors (@typescript-eslint/no-extra-semi) on lines 43 and 76. The leading semicolons before the chargebeeInstance type casts were flagged as unnecessary by ESLint and have been removed. This fixes the CI pipeline failure in PR #2143. * chore: refacto to avoid use of any * fix: remove any on tests * clean-up * fix: variable css add credit card modal --------- Co-authored-by: RemiBonnet <bonnet.rem@gmail.com>
21 days ago by acarranoqo...