feat: Wcp.FeatureFlags extension and extension infrastructure consolidation by Copilot · Pull Request #4950 · webiny/webiny-js

Copilot · 2026-02-20T10:11:29Z

Adds a Wcp.FeatureFlags extension that lets users override WCP feature flags at the project-config level (webiny.config.tsx), independently of the fetched WCP license. Useful for disabling licensed features in dev/staging environments while keeping them active in production.

Usage

import { Wcp } from "webiny/extensions";

export const Extensions = () => (
  <>
    <Wcp.FeatureFlags
      features={{
        advancedAccessControlLayer: { enabled: false, options: { teams: false } },
        advancedPublishingWorkflow: { enabled: false }
      }}
    />
  </>
);

The features prop mirrors the WCP license structure. Supported keys:

Key	Sub-options
`multiTenancy`	`enabled`
`advancedPublishingWorkflow`	`enabled`
`advancedAccessControlLayer`	`enabled`, `options.teams`, `options.privateFiles`, `options.folderLevelPermissions`
`auditLogs`	`enabled`
`recordLocking`	`enabled`
`fileManager`	`options.threatDetection`

Users can only disable features — attempting to enable a feature the WCP license does not permit has no effect (overrides are ANDed with the license value).

Changes

New: `Wcp.FeatureFlags` extension (`packages/project/src/extensions/FeatureFlags.tsx`)

Defined in packages/project using the render method pattern (same as Cognito.tsx)
File named FeatureFlags.tsx (generic — future non-WCP feature flags can be added here)
render outputs two build params — <ApiBuildParam paramName="FeatureFlags" value={{ wcp: features }} /> and <AdminBuildParam paramName="FeatureFlags" value={{ wcp: features }} /> — delegating all file-generation to the existing build infrastructure
The entire feature flags object is stored under the single "FeatureFlags" build param key as { wcp: { ... } }
Zod schema validation mirrors the IFeatureFlags shape from @webiny/feature-flags
Exported as export const Wcp = { FeatureFlags: ... } (consistent with EnvVar.ts pattern)
Extension registered via Wcp.FeatureFlags.def in packages/project/src/extensions/index.ts

New: `IFeatureFlags` interface (`packages/feature-flags/src/index.ts`)

Bare-bones package with no @webiny/* dependencies — easy to include in packages/project, packages/api-core, and packages/app-admin
IFeatureFlags { wcp?: { ... } } — extensible top-level interface for all feature flag namespaces

New: `FeatureFlags` feature (`packages/api-core`)

packages/api-core/src/features/wcp/WcpFeatureFlags/ — FeatureFlagsImpl class (abstraction: FeatureFlagsAbstraction) reads buildParams.get<IFeatureFlags>("FeatureFlags") and maps WCP feature names to their nested path under .wcp; registered as WcpFeatureFlagsFeature
WcpContextWithFeatureFlagsDecorator (WcpContextWithFeatureFlagsDecorator.ts) — decorator (open/closed principle) that wraps WcpContext and applies FeatureFlags checks to all canUse* methods via WcpContextWithFeatureFlagsDecoratorImpl; WcpContextImpl is unchanged

Updated: Admin WCP feature checks respect feature flags

Wcp.tsx (packages/app-admin) — all CanUse* components read the "FeatureFlags" build param typed as IFeatureFlags via useContainer() and AND the result with the license check

Consolidated: Extension primitives moved to `packages/project`

packages/api-core/src/extensions/BuildParam.ts → packages/project/src/extensions/ApiBuildParam.ts
packages/api-core/src/extensions/GenericExtension.ts → packages/project/src/extensions/ApiExtension.ts
packages/app-admin/src/extensions/AdminBuildParam.ts → packages/project/src/extensions/AdminBuildParam.ts
packages/app-admin/src/extensions/AdminExtension.ts → packages/project/src/extensions/AdminExtension.ts
No backwards-compatibility shims — originals removed; packages/app-admin/src/extensions/index.ts, packages/api-core/src/extensions/index.ts, and the entire packages/api-core/src/extensions/eventHandlers/ folder deleted — event handler registration is now handled entirely via Api.Extension
packages/project-aws/src/security.ts deleted — Security.* event handler namespace removed; use Api.Extension instead
packages/project-aws updated to import BuildParam, AdminBuildParam, AdminExtension, and ApiExtension from @webiny/project

Exports

Wcp exported via packages/project/src/exports/extensions.ts → packages/project-aws/src/exports/extensions.ts → packages/webiny/src/extensions.ts

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

…gn export naming Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

adrians5j · 2026-02-20T10:51:10Z

packages/project/src/extensions/WcpFeature.ts

+    tags: { runtimeContext: "app-build", appName: "api" },
+    multiple: true,
+    paramsSchema,
+    async build(params, ctx) {


This sux. rather use render method like

packages/cognito/src/Cognito.tsx:14

this easily allows you to reuse existing Api.BuildParam and Admin.BuildParams. @copilot

Refactored in e76b322. Moved Wcp.Feature to packages/project-aws/src/wcp.tsx and rewrote it using the render method pattern — it now simply renders <Api.BuildParam> and <Admin.BuildParam> with the wcp.feature.{name} param key, delegating all file-generation to the existing build logic. Removed all custom ts-morph/fs code.

….Feature Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

adrians5j

@copilot

adrians5j · 2026-02-20T12:13:13Z

packages/api-core/src/features/wcp/WcpContext/WcpContext.ts

-    constructor(private license: ILicense) {}
+    constructor(
+        private license: ILicense,
+        private buildParams?: IBuildParams


? not needed.

Fixed in c9cb6fa — WcpContextImpl is back to its original form with no ? and no BuildParams.

adrians5j · 2026-02-20T12:14:29Z

packages/api-core/src/features/wcp/WcpContext/WcpContext.ts


    canUsePrivateFiles(): boolean {
-        return this.license.canUsePrivateFiles();
+        return this.license.canUsePrivateFiles() && this.isFeatureEnabled("privateFiles");


Instead of directly involving BuildParams here, let's rather do an intermediary abstraction, called maybe something like WcpFeatureSwitcher. Or maybe you make a better name for the abstraction. IDK any other name.

Then, let's use open/closed principle. Instead of modifying, let's rather create a WcpContext decorator, which adds this extra WcpFeatureSwitcher layer of functionality.

Done in c9cb6fa. Introduced WcpFeatureOverrides abstraction (packages/api-core/src/features/wcp/WcpFeatureOverride/) that reads wcp.feature.{name} build params, and a WcpContextWithFeatureOverrides decorator (WcpContext/decorators/) that wraps WcpContext and applies the overrides to all canUse* methods — without touching WcpContextImpl at all. Registered via WcpFeature.ts.

…hFeatureOverrides decorator Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

adrians5j · 2026-02-20T13:15:42Z

You know what... I just made up my mind..

Instead of writing multiple

<Wcp.Feature name="teams" enabled={false} />
    <Wcp.Feature name="workflows" enabled={false} />`.. let's rather have smt like

 <Wcp.FeatureFlags features={{ advancedAccessControLayer: { enabled: false, options: { teams: false }} }} />

Basically the same structure of license I mentioned, which then gets merged with this config here.

The most important thing when doing the merge ofc is preventing users from allowng a feature via this comp, and being able to use it, despite real fetched license saying the feat is not allowed. @copilot

Copilot · 2026-02-20T13:16:33Z

You know what... I just made up my mind..

Instead of writing multiple ` <Wcp.Feature name="teams" enabled={false} />
...

The comment appears to have been truncated — the code block didn't come through. Could you share the full suggestion?

adrians5j · 2026-02-20T13:21:54Z

pasting comment again

You know what... I just made up my mind..

Instead of writing multiple

<Wcp.Feature name="teams" enabled={false} />
    <Wcp.Feature name="workflows" enabled={false} />`.. let's rather have smt like

 <Wcp.FeatureFlags features={{ advancedAccessControLayer: { enabled: false, options: { teams: false }} }} />

Basically the same structure of license I mentioned, which then gets merged with this config here.

The most important thing when doing the merge ofc is preventing users from allowng a feature via this comp, and being able to use it, despite real fetched license saying the feat is not allowed. @copilot

@copilot

Copilot · 2026-02-20T13:22:36Z

pasting comment again

You know what... I just made up my mind..
...

Still getting a truncated code block — the content after ```tsx isn't coming through. Could you try posting the code example as plain text or in a new comment?

adrians5j · 2026-02-20T13:38:45Z

pasting comment again

You know what... I just made up my mind..

Instead of writing multiple

<Wcp.Feature name="teams" enabled={false} />
<Wcp.Feature name="workflows" enabled={false} />`.. let's rather have smt like

<Wcp.FeatureFlags features={{ advancedAccessControLayer: { enabled: false, options: { teams: false }} }} />

Basically the same structure of license I mentioned, which then gets merged with this config here.

The most important thing when doing the merge ofc is preventing users from allowng a feature via this comp, and being able to use it, despite real fetched license saying the feat is not allowed. @copilot

@copilot

adrians5j · 2026-02-25T11:10:33Z

update PR body.. I made soem changes @copilot

adrians5j · 2026-02-25T11:37:51Z

let's write PR body from scratch @copilot

Copilot · 2026-02-25T11:39:37Z

let's write PR body from scratch @copilot

Done — PR body rewritten from scratch.

adrians5j · 2026-03-02T10:58:49Z

/e2e

github-actions · 2026-03-02T10:58:58Z

Cypress E2E tests have been initiated (for more information, click here). ✨

adrians5j · 2026-03-02T11:06:32Z

/e2e

github-actions · 2026-03-02T11:06:47Z

Cypress E2E tests have been initiated (for more information, click here). ✨

adrians5j · 2026-03-02T12:06:33Z

/e2e

github-actions · 2026-03-02T12:06:47Z

Cypress E2E tests have been initiated (for more information, click here). ✨

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com> Co-authored-by: Adrian Smijulj <adrian1358@gmail.com> Co-authored-by: adrians5j <adrian@webiny.com>

Initial plan

0834069

Copilot AI assigned Copilot and adrians5j Feb 20, 2026

Copilot started work on behalf of adrians5j February 20, 2026 10:11 View session

Copilot AI and others added 2 commits February 20, 2026 10:40

feat: add Wcp.Feature component for enabling/disabling WCP features

8efc6cd

Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

fix: address code review - use container.resolve for BuildParams, ali…

50038e6

…gn export naming Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

Copilot AI changed the title ~~[WIP] Add conditional rendering for tenant management extensions~~ feat: Wcp.Feature component for user-controlled WCP feature overrides Feb 20, 2026

Copilot AI requested a review from adrians5j February 20, 2026 10:49

Copilot finished work on behalf of adrians5j February 20, 2026 10:49

adrians5j reviewed Feb 20, 2026

View reviewed changes

Copilot started work on behalf of adrians5j February 20, 2026 10:51 View session

refactor: use render method + Api.BuildParam/Admin.BuildParam for Wcp…

e76b322

….Feature Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

Copilot AI requested a review from adrians5j February 20, 2026 11:01

Copilot finished work on behalf of adrians5j February 20, 2026 11:01

adrians5j requested changes Feb 20, 2026

View reviewed changes

Copilot started work on behalf of adrians5j February 20, 2026 12:14 View session

refactor: introduce WcpFeatureOverrides abstraction and WcpContextWit…

c9cb6fa

…hFeatureOverrides decorator Co-authored-by: adrians5j <5121148+adrians5j@users.noreply.github.com>

Copilot finished work on behalf of adrians5j February 20, 2026 12:21

Copilot AI requested a review from adrians5j February 20, 2026 12:21

Copilot started work on behalf of adrians5j February 20, 2026 13:16 View session

Copilot finished work on behalf of adrians5j February 20, 2026 13:17

Merge branch 'next' into copilot/add-multi-tenancy-condition

f92adb0

Copilot started work on behalf of adrians5j February 20, 2026 13:22 View session

Pavel910 added this to the 6.0.0 milestone Feb 20, 2026

Copilot finished work on behalf of adrians5j February 20, 2026 13:23

Copilot started work on behalf of adrians5j February 25, 2026 11:10 View session

Copilot AI changed the title ~~feat: Wcp.FeatureFlags component and extension infrastructure consolidation~~ feat: FeatureFlags extension and extension infrastructure consolidation Feb 25, 2026

Copilot finished work on behalf of adrians5j February 25, 2026 11:14

Copilot started work on behalf of adrians5j February 25, 2026 11:38 View session

Copilot AI changed the title ~~feat: FeatureFlags extension and extension infrastructure consolidation~~ feat: Wcp.FeatureFlags extension and extension infrastructure consolidation Feb 25, 2026

Copilot finished work on behalf of adrians5j February 25, 2026 11:40

adrians5j added 6 commits February 27, 2026 21:33

wip:8 (laji5)

b891884

wip:9 (oo9zb)

7ada057

wip:10 (21egc)

41e20f2

wip:11 (zu7lz)

b254608

wip:12 (rgde9)

70bd49b

wip:13 (zf32f)

dc6c0fe

adrians5j marked this pull request as ready for review March 2, 2026 10:58

Merge branch 'next' into copilot/add-multi-tenancy-condition

4239cd5

adrians5j added 3 commits March 2, 2026 12:21

wip:14 (t1ix5)

f227c85

wip:15 (45vkq)

eb583a2

wip:16 (w8amu)

f1ecc75

adrians5j merged commit 63729ba into next Mar 3, 2026
18 checks passed

adrians5j deleted the copilot/add-multi-tenancy-condition branch March 5, 2026 08:21

Conversation

Copilot AI commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Usage

Changes

New: Wcp.FeatureFlags extension (packages/project/src/extensions/FeatureFlags.tsx)

New: IFeatureFlags interface (packages/feature-flags/src/index.ts)

New: FeatureFlags feature (packages/api-core)

Updated: Admin WCP feature checks respect feature flags

Consolidated: Extension primitives moved to packages/project

Exports

Uh oh!

adrians5j Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

adrians5j left a comment

Choose a reason for hiding this comment

Uh oh!

adrians5j Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

adrians5j Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 20, 2026

Choose a reason for hiding this comment

Uh oh!

adrians5j commented Feb 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI commented Feb 20, 2026

Uh oh!

adrians5j commented Feb 20, 2026

Uh oh!

Copilot AI commented Feb 20, 2026

Uh oh!

adrians5j commented Feb 20, 2026

Uh oh!

adrians5j commented Feb 25, 2026

Uh oh!

adrians5j commented Feb 25, 2026

Uh oh!

Copilot AI commented Feb 25, 2026

Uh oh!

adrians5j commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026

Uh oh!

adrians5j commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026

Uh oh!

adrians5j commented Mar 2, 2026

Uh oh!

github-actions bot commented Mar 2, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Copilot AI commented Feb 20, 2026 •

edited

Loading

New: `Wcp.FeatureFlags` extension (`packages/project/src/extensions/FeatureFlags.tsx`)

New: `IFeatureFlags` interface (`packages/feature-flags/src/index.ts`)

New: `FeatureFlags` feature (`packages/api-core`)

Consolidated: Extension primitives moved to `packages/project`

adrians5j commented Feb 20, 2026 •

edited

Loading