feat(registry): seed FuzeSocial as builtin — adds Social to nav - #344
Merged
Conversation
…hart Add GOOGLE_CLIENT_ID/GOOGLE_CLIENT_SECRET (secretKeyRef, optional:true), GOOGLE_REDIRECT_URI, and SECURITY_GOOGLE_BROKERED kill-switch to the fuzefront-security container for the brokered Google flow (PR #329). Prod enables it (googleBrokered "true"); flip to "false" for instant rollback to the legacy Authentik source flow with no rebuild. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session-Id: f636c22e-1cd7-401e-8843-97e3e3a4ba01
Adds FuzeSocial to BUILTIN_MANIFESTS so the applications-service seeds it idempotently on every boot. The app shows as "Social" in the host shell nav and loads via iframe pointing at: https://social.prod.fuzefront.com Integration type: iframe (the shell already supports this in FederatedAppLoader.tsx — renders a full-viewport iframe for the URL). visibility: organization so it appears to authenticated org members. Also adds the reference seed JSON at: services/app-registry-service/seed/fuzesocial.manifest.json No feature flag needed — builtin seeding is always-on. The `fuzesocial` row is inserted with `builtin:true, status:activated` so it shows immediately in the nav on next pod restart. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session-Id: 86000e5d-af71-4821-9e4a-dec0ee1ec6e4
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
1 participant
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.
Summary
BUILTIN_MANIFESTSinbuiltins.tsso the applications-service seeds it idempotently on every boothttps://social.prod.fuzefront.comin a full-viewport iframeFederatedAppLoader.tsxalready handlestype: iframe— no frontend changes neededservices/app-registry-service/seed/fuzesocial.manifest.jsonHow it works
ensureBuiltins()is called at every applications-service boot. It upserts each entry inBUILTIN_MANIFESTSwithbuiltin:true, status:activated. Existing rows are skipped (idempotent). On next pod restart thefuzesocialrow appears in the DB and the shell lists it in the nav.Test plan
kubectl rollout restart deployment/fuzefront-applications -n fuzefront)fuzesocialrow inappstable:SELECT slug, status, builtin FROM apps WHERE slug = 'fuzesocial';https://app.fuzefront.com→ "Social" appears in the left nav / 9-dots launcherhttps://social.prod.fuzefront.comin the iframe🤖 Generated with Claude Code