feat(api): add listed_in_marketplace flag to store apps - #260
Merged
Conversation
…pi/regions visibility
dan2k3k4
marked this pull request as ready for review
August 18, 2026 16:18
dan2k3k4
enabled auto-merge
August 18, 2026 16:26
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The AWS Marketplace amazeeClaw flow needs its store apps
available+available_for_trialsso/api/registeraccepts them, and it enumerates regions via the publicGET /api/regions. The regular apps (Dependency Track, AnythingLLM, non-AWS claws) should no longer be exposed on that unauthenticated endpoint. Until now visibility was only controllable per store, not per app.What
listed_in_marketplaceboolean onpolydock_store_apps, default false.GET /api/regionsnow only lists apps withlisted_in_marketplace = true(in addition to the existing app-available + store-public+listed filters)./api/regionskeeps working in dev./api/store-apps(unchanged) and filters by Stripe product mapping.Rollout note
Existing rows default to false, so after migrating,
/api/regionsreturns empty app lists until the intended apps (the fiveamazeeClaw - AWS (*)store apps) are flipped on via the admin panel or SQL.Testing
/api/regions.Greptile Summary
The PR adds per-app control over inclusion in the unauthenticated marketplace catalog while leaving authenticated store-app access and registration eligibility unchanged.
listed_in_marketplacedatabase field, model assignment support, and boolean casting.GET /api/regionsusing the new flag.Confidence Score: 5/5
The PR appears safe to merge, with the temporary empty-catalog rollout behavior explicitly documented and controllable through the admin panel.
The new schema field is consistently wired through persistence and administration, and the public catalog applies the intended default-deny app filter with focused regression coverage.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart LR Client["Public client"] --> Regions["GET /api/regions"] Regions --> Stores{"Store is public<br/>and listed"} Stores --> Apps{"App is available<br/>and listed"} Apps -->|Yes| Catalog["Return app in region catalog"] Apps -->|No| Hidden["Exclude app"] Admin["Filament admin"] --> Flag["listed_in_marketplace"] Flag --> AppsReviews (1): Last reviewed commit: "feat(api): add listed_in_marketplace fla..." | Re-trigger Greptile
Context used (3)