Prevent telemetry disabling in OSS edition without WCP connection

[Copilot]

OSS users must not disable telemetry unless connected to Webiny Control Panel (enterprise feature) or working in the webiny-js development repository.

Changes

• Added IsWcpEnabled abstraction and implementation: Created new abstraction to check WCP connection status using GetProjectIdService instead of direct environment variable access. Provides cleaner separation of concerns and better testability.

• Added IsWebinyJsRepo abstraction and implementation: Created new abstraction to detect the webiny-js development repository by checking for the existence of packages/admin-ui directory. This allows developers working on Webiny itself to bypass telemetry restrictions.

• Added EnsureTelemetryEnabledForOss BeforeDeploy hook: Validates telemetry state before deployment by checking IsTelemetryEnabled, IsWcpEnabled, and IsWebinyJsRepo services. Throws GracefulError when telemetry is disabled without WCP connection in non-development environments.

• Registered built-in implementations in DI container: Auto-loaded in createProjectSdkContainer.ts after composite registration, ensuring validation runs on every deployment without requiring explicit user configuration.

Behavior

// webiny-js dev repo - validation skipped
<Project.Telemetry enabled={false} />  // ✓ Deploys successfully (dev environment)

// OSS user without WCP - deployment blocked
<Project.Telemetry enabled={false} />  
// Error: "You are trying to disable telemetry in the open-source edition..."

// Enterprise user with WCP - allowed
WCP_PROJECT_ID="org/proj"
<Project.Telemetry enabled={false} />  // ✓ Deploys successfully

Pattern follows existing built-in hooks like EnsureCoreDeployedBeforeApiDeploy and uses proper abstractions for improved maintainability.

Original prompt

i need to impl the following req

• if someone who is on the open-source version tries to disable it, to throw an error during the build saying that this cannot be done in the OSS edition of Webiny

Basically, we want to check if WCP is connected. If so, then allow disable telemery (via <Project.Telemetry enabled={false} />, as seen in #file:webiny.config.tsx

If not WCP connected, then throw an error.

Notes:

• we want to do this in a before-deploy hook (BeforeDeploy abs)
• you can use #file:EnsureCoreDeployedBeforeApiDeploy.ts
• you can use const wcpProjectId = process.env.WCP_PROJECT_ID || ""; as seen in #file:ProjectInfoService to determine whether WCP conn exists

The user has attached the following files from their workspace:

• webiny.config.tsx
• packages/project/src/extensions/Project/EnsureCoreDeployedBeforeApiDeploy.ts
• packages/project/src/services/ProjectInfoService

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[adrians5j]

let's do one more thing here...

In packages/project/src/extensions/Project/EnsureTelemetryEnabledForOss.ts:9, let's actually use IsWcpEnabled abstraction. It does not exist, you need to create it.

Also, let's do one other abstraction and that's IsWebinyJsRepo. Basically, we need to distiguish between real Webiny project and a webiny-js dev repo (repo where Webiny is developed). The impl basically checks existence of packages/admin-ui pkg. For example I had this the other day

 const adminUiPkgPath = path.join(projectRootFolderPath, "packages", "admin-ui");

    const isWebinyJsRepo = fs.existsSync(adminUiPkgPath);

Once we have that abs/impl, then use it in the new EnsureTelemetryEnabledForOss impl. Basically, we don't care on what tier the project is when webiny-js repo === true.

@copilot

[Copilot]

let's do one more thing here...

In packages/project/src/extensions/Project/EnsureTelemetryEnabledForOss.ts:9, let's actually use IsWcpEnabled abstraction. It does not exist, you need to create...

Done! Created IsWcpEnabled and IsWebinyJsRepo abstractions and updated EnsureTelemetryEnabledForOss to use them. The implementation now:

• Uses IsWcpEnabled instead of direct env var check
• Skips validation for webiny-js dev repo using IsWebinyJsRepo
• Follows the exact pattern you provided for detecting the dev repo

Commit: fd435af