feat: gate custom branding behind license field (Tier 4.7)#42
Merged
aa-replicated merged 1 commit intomainfrom Apr 13, 2026
Merged
feat: gate custom branding behind license field (Tier 4.7)#42aa-replicated merged 1 commit intomainfrom
aa-replicated merged 1 commit intomainfrom
Conversation
Adds a custom_branding_enabled license field gate across the full stack: - kots-config.yaml: new Branding config group (site_color item) hidden via group-level when: condition using LicenseFieldValue - helmchart.yaml: passes siteColor (ConfigOption) and customBrandingEnabled (LicenseFieldValue) into Helm values - values.yaml: siteColor and customBrandingEnabled defaults - configmap.yaml / deployment.yaml: site-color and custom-branding-enabled env vars wired to the app - config.go: SiteColor and CustomBrandingEnabled fields loaded from env - handlers.go: CustomBrandingEnabled on PageData (set in pageBase); SiteColor replaces hardcoded #3B82F6 default - admin.go: updateBrandingHandler and uploadLogoHandler return 403 when custom branding is not licensed - admin.html: Branding and Logo sections hidden when not licensed Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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
custom_branding_enabledlicense field gate across the full stackChanges
kots-config.yamlbrandinggroup withsite_coloritem, hidden via group-levelwhen: '{{repl LicenseFieldValue "custom_branding_enabled" | eq "true"}}'helmchart.yamlsiteColor(ConfigOption) andcustomBrandingEnabled(LicenseFieldValue) passed into Helm valuesvalues.yamlsiteColor: "#3B82F6"andcustomBrandingEnabled: "false"defaultsconfigmap.yaml/deployment.yamlSITE_COLORandCUSTOM_BRANDING_ENABLEDenv varsconfig.goSiteColorandCustomBrandingEnabledfields loaded from envhandlers.goCustomBrandingEnabledonPageData(set inpageBase);SiteColorreplaces hardcoded#3B82F6defaultadmin.goupdateBrandingHandleranduploadLogoHandlerreturn 403 when not licensedadmin.htmlCustomBrandingEnabledis falseTest plan
custom_branding_enabledis absent/false — Branding group hidden in KOTS config screen, Branding + Logo sections absent from admin panelcustom_branding_enabled: true, trigger upgrade — Branding group appears in config screen, sections visible in admin panel, branding changes save correctlyPOST /admin/brandingandPOST /admin/logoreturn 403 when not licensedManual step required
Create a
custom_branding_enabledlicense field in the Vendor Portal (type: boolean or string"true"/"false") before testing.🤖 Generated with Claude Code