feat: add Premium Geo DB addon to project settings by lohanidamodar · Pull Request #2981 · appwrite/console

lohanidamodar · 2026-04-18T10:19:27Z

Summary

Adds a Premium Geo DB section to the project settings page so users can enable and disable the premium geolocation addon per-project on cloud.

The section supports the full addon lifecycle, mirroring the BAA pattern at the organization level:

Upgrade prompt when the current plan does not support the addon
Enable flow with optional 3DS payment authentication
Pending state with cancel & retry option (if payment was interrupted)
Active state with disable action
Scheduled-for-removal state with re-enable action

Uses the new project-scoped SDK methods shipped with the cloud update: listAddons, createPremiumGeoDBAddon, and deleteAddon. Bumps the @appwrite.io/console SDK pin accordingly.

Test plan

Navigate to a cloud project's settings as an org owner on a plan that supports Premium Geo DB → section appears with Enable CTA
Click Enable → modal confirms and enables the addon (3DS where required); section transitions to Active
Click Disable → confirms removal at end of billing cycle; section transitions to Scheduled-for-removal
Click Keep Premium Geo DB while Scheduled-for-removal → returns to Active
On a plan that doesn't support the addon → shows Upgrade plan CTA / "not available" copy
On self-hosted mode → section is hidden

🤖 Generated with Claude Code

Adds a Premium Geo DB section to the project settings page so users can enable and disable the premium geolocation addon per-project on cloud. The section supports the full addon lifecycle: - Upgrade prompt when the current plan does not support the addon - Enable flow with optional 3DS payment authentication - Pending state with cancel & retry option - Active state with disable action - Scheduled-for-removal state with re-enable action Uses the new project-scoped SDK methods: listAddons, createPremiumGeoDBAddon, and deleteAddon. Bumps the @appwrite.io/console SDK pin accordingly. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

greptile-apps · 2026-04-18T10:21:46Z

Greptile Summary

This PR adds a Premium Geo DB addon section to the project settings page, enabling users to enable, disable, and manage the addon's full lifecycle (pending, active, scheduled-for-removal). It also bumps the @appwrite.io/console SDK pin and updates several address/billing components from Models.Locale to Models.CloudLocale.

New premiumGeoDB.svelte component and its enable/disable modals mirror the existing BAA pattern, including an onMount handler for 3DS redirect return and graceful degradation when addon/price APIs fail.
planSummary.svelte removes the hardcoded billingAddonNames map and adds per-project addon charge rows to the project breakdown section.
Six unrelated address/billing Svelte files receive a mechanical Models.Locale \u2192 Models.CloudLocale type-only update.

Confidence Score: 3/5

The addon state detection may silently fail if the API key casing does not match the camelCase string used in the filter, combined with unresolved payment flow gaps in the enable modal.

The core addon state detection in premiumGeoDB.svelte filters by a camelCase key string inconsistent with the all-lowercase key used by the established BAA component. If the API returns a lowercase key, both the reactive state derivation and the onMount fallback lookup would silently produce undefined, making isPending, isActive, and isScheduledForRemoval always false. The enable modal also has several open gaps from prior review rounds.

premiumGeoDB.svelte (addon key string) and premiumGeoDBEnableModal.svelte (payment flow gaps) need the most attention before this ships.

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/settings/premiumGeoDB.svelte	New component implementing the Premium Geo DB addon lifecycle; has an onMount 3DS return handler, but the addon key string 'premiumGeoDB' is camelCase and may not match what the API returns (BAA uses lowercase 'baa'), which would silently break all addon state detection.
src/routes/(console)/project-[region]-[project]/settings/premiumGeoDBEnableModal.svelte	New enable modal; missing redirectIfRequired: true in confirmPayment and does not inspect the outcome; also missing the !addonPrice guard on the submit button that BAAEnableModal uses to prevent enabling before the price is loaded.
src/routes/(console)/project-[region]-[project]/settings/premiumGeoDBDisableModal.svelte	New disable modal; straightforward implementation calling deleteAddon and invalidating dependencies on success. No issues found.
src/routes/(console)/project-[region]-[project]/settings/+page.ts	Adds listAddons and getAddonPrice calls guarded by isCloud, using .catch to null for graceful degradation. Removed helpful comments explaining why read-only permission errors are silenced.
src/routes/(console)/project-[region]-[project]/settings/+page.svelte	Adds PremiumGeoDB section inside isCloud and canWriteProjects guard. Clean integration.
src/routes/(console)/organization-[organization]/billing/planSummary.svelte	Removes hardcoded billingAddonNames map in favour of addon.name (risks blank label if API omits name), and adds per-project addon rows that may double-count charges already present in the top-level addons aggregation.
src/routes/(console)/organization-[organization]/settings/Soc2.svelte	Type update from Models.Locale to Models.CloudLocale, matching the same change made to all other address/billing Svelte files in this PR.

_{Reviews (20): Last reviewed commit: "fix: rename Models.Locale to Models.Clou..." | Re-trigger Greptile}

Mirrors the BAA addon UX by fetching the addon price via organizations.getAddonPrice(Addon.Premiumgeodb) from the settings page loader, passing it through to the Premium Geo DB card and enable modal, and rendering the monthly/prorated breakdown with formatCurrency alongside the Enable CTA. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…name - Each project row in the organization billing breakdown now iterates its resources for addon_* entries (amount > 0) and renders them as child rows (e.g. Premium Geo DB under the project it was enabled on). The backend already filters project-scoped addons out of the team-level resources response, so the org "Addons" section shows only org-scoped addons (BAA, premiumGeoDBOrg) while project-scoped ones surface where they belong. - Org-level addon labels now read addon.name from the UsageResource payload that the getAggregation endpoint populates from billingAddons config. Dropped the hard-coded billingAddonNames map so new addons surface with their proper name without a console update. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

…geo-db-addon

…geo-db-addon # Conflicts: # bun.lock # package.json # src/routes/(console)/project-[region]-[project]/settings/+page.svelte

…geo-db-addon # Conflicts: # bun.lock # package.json

…DK methods" This reverts commit 304142c.

…geo-db-addon # Conflicts: # src/routes/(console)/project-[region]-[project]/settings/+page.svelte # src/routes/(console)/project-[region]-[project]/settings/+page.ts

greptile-apps · 2026-04-30T02:58:50Z

+                    ...resources
+                        .filter((r) => r.resourceId?.startsWith('addon_') && (r.amount ?? 0) > 0)
+                        .map((addon) =>
+                            createRow({
+                                id: `addon-${addon.resourceId}`,
+                                label: addon.name || addon.resourceId,
+                                resource: addon,
+                                usageFormatter: ({ value }) => formatNum(value),
+                                priceFormatter: ({ amount }) => formatCurrency(amount),
+                                includeProgress: false
+                            })
+                        ),


Possible double-counting of addon charges in plan summary

The top-level addons section (line 252–275) already creates a billing row for every addon_-prefixed resource found in currentAggregation.resources. If the billing API also surfaces those same addon resources inside projectData.resources (the per-project breakdown), each project-scoped addon (e.g. Premium Geo DB) will appear as both a top-level line item and a child row — showing the same charge twice to the user.

Before shipping, confirm whether the cloud billing API places project-level addon charges exclusively in breakdown[].resources (making the top-level filter skip them) or in both places. If the former, this code is correct; if the latter, the top-level addons filter needs to exclude resources that are already accounted for at the project level (or vice-versa).

…geo-db-addon # Conflicts: # bun.lock # package.json

…eveloper value

…ariant

…geo-db-addon # Conflicts: # bun.lock # package.json

…geo-db-addon

…h for premium geoDB Two missing pieces vs the BAA addon flow: 1. After Stripe redirects back from 3DS with ?type=confirm-addon&addonId=..., the page didn't read the query params or call the confirmations endpoint, so the addon stayed pending forever. Port the onMount handler from BAA.svelte. 2. The pending-state action was "Cancel & retry" which deleted the addon and forced a fresh 3DS flow. That's wasteful when the payment just needs a server-side status sync. Replace with "Refresh" — calls the confirmations endpoint, which live-queries Stripe and activates the addon if the PaymentIntent has transitioned to succeeded. Backend cleans up on 402.

…geo-db-addon

The console SDK bump in this PR renamed Locale to CloudLocale, breaking svelte-check with 7 errors across billing/Soc2/address components.

greptile-apps · 2026-05-17T03:58:51Z

+    );
+    $: isPending = premiumGeoDBAddon?.status === 'pending';
+    $: isActive = premiumGeoDBAddon?.status === 'active';


Addon key casing inconsistency with BAA pattern

The BAA.svelte filter uses the all-lowercase string 'baa', consistent with Appwrite's API key convention. Here 'premiumGeoDB' (camelCase) is used. If the API returns the addon with a lowercase key (following the same pattern as BAA), this find will never match — premiumGeoDBAddon would always be undefined and the component would always render the Enable CTA even when the addon is already active or pending. The same camelCase string is also used in the onMount fallback lookup at line 65, so both detection paths would silently fail. Please confirm the exact key string the API returns for this addon. What string does the API's listAddons response return for the key field of the Premium Geo DB addon — 'premiumGeoDB', 'premiumgeodb', or something else? BAA uses 'baa' (all lowercase), so camelCase here looks inconsistent with that established pattern.

greptile-apps Bot reviewed Apr 18, 2026

View reviewed changes

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDB.svelte

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDB.svelte

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDB.svelte

lohanidamodar and others added 4 commits April 19, 2026 11:13

update sdk

7e73d36

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

66e615e

…geo-db-addon

greptile-apps Bot reviewed Apr 20, 2026

View reviewed changes

Comment thread src/routes/(console)/organization-[organization]/billing/planSummary.svelte

lohanidamodar added 8 commits April 21, 2026 04:34

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

afb13fc

…geo-db-addon

chore: bump @appwrite.io/console SDK to 95547fc

13b0478

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

0cba797

…geo-db-addon # Conflicts: # bun.lock # package.json # src/routes/(console)/project-[region]-[project]/settings/+page.svelte

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

6fc000f

…geo-db-addon # Conflicts: # bun.lock # package.json

chore: keep @appwrite.io/console@95547fc for premium geo DB SDK methods

304142c

Revert "chore: keep @appwrite.io/console@95547fc for premium geo DB S…

67566db

…DK methods" This reverts commit 304142c.

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

e5a62c5

…geo-db-addon # Conflicts: # src/routes/(console)/project-[region]-[project]/settings/+page.svelte # src/routes/(console)/project-[region]-[project]/settings/+page.ts

chore: update console SDK to 352239b

a54c530

greptile-apps Bot reviewed Apr 30, 2026

View reviewed changes

lohanidamodar added 5 commits May 4, 2026 02:45

merge main

4376702

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

da68f75

…geo-db-addon # Conflicts: # bun.lock # package.json

feat(settings): rewrite Premium Geo DB card description to focus on d…

0889ace

…eveloper value

feat(settings): tighten Premium Geo DB card copy to outcome-focused v…

6fbdd43

…ariant

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

1ba8ebd

…geo-db-addon # Conflicts: # bun.lock # package.json

greptile-apps Bot reviewed May 11, 2026

View reviewed changes

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDBEnableModal.svelte

chore: update console SDK to 634f110

f8d2816

greptile-apps Bot reviewed May 11, 2026

View reviewed changes

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDBEnableModal.svelte

lohanidamodar added 2 commits May 12, 2026 05:59

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

afecbd2

…geo-db-addon

greptile-apps Bot reviewed May 12, 2026

View reviewed changes

Comment thread src/routes/(console)/project-[region]-[project]/settings/premiumGeoDB.svelte

lohanidamodar added 2 commits May 13, 2026 03:43

Merge remote-tracking branch 'origin/main' into feat/project-premium-…

279737d

…geo-db-addon

fix: rename Models.Locale to Models.CloudLocale after SDK bump

51ad756

The console SDK bump in this PR renamed Locale to CloudLocale, breaking svelte-check with 7 errors across billing/Soc2/address components.

greptile-apps Bot reviewed May 17, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: add Premium Geo DB addon to project settings#2981

feat: add Premium Geo DB addon to project settings#2981
lohanidamodar wants to merge 23 commits into
mainfrom
feat/project-premium-geo-db-addon

lohanidamodar commented Apr 18, 2026

Uh oh!

greptile-apps Bot commented Apr 18, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot Apr 30, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot May 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

lohanidamodar commented Apr 18, 2026

Summary

Test plan

Uh oh!

greptile-apps Bot commented Apr 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Greptile Summary

Confidence Score: 3/5

Important Files Changed

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot Apr 30, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

greptile-apps Bot May 17, 2026

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

greptile-apps Bot commented Apr 18, 2026 •

edited

Loading