sample_on_prem_config.json points to api-staging.codesync.com — leaks on-prem customer data to CodeSync staging

[chirag127]

Problem

sample_on_prem_config.json — the template on-prem customers copy — hardcodes CodeSync's staging cloud hosts instead of placeholder values. On-prem customers who copy the sample and forget to edit will send code/diffs to api-staging.codesync.com, defeating the whole point of on-prem (data isolation).

File cite

sample_on_prem_config.json lines 1-6:

{
	"API_HOST": "https://api-staging.codesync.com", 
	"SOCKET_HOST": "wss://api-staging.codesync.com",
	"WEBAPP_HOST": "https://staging.codesync.com",
	"AWS_REGION": "us-east-1",
	"CW_LOGS_GROUP": "/codesync/plugin-logs"
}

CHANGELOG.md line 22 confirms v4.3.0 (2024-10-23) added on-prem support and this sample file.

Expected

Sample values should be obvious placeholders, e.g. https://your-onprem-host.example.com, so copy-without-edit fails loudly rather than silently sending data to CodeSync staging.

Actual

Valid staging endpoints. Plugin loads without error; data flows to CodeSync's staging AWS account.

Environment

codesync-vs v4.10.1 (package.json v4.10.1), Node 20.11.0, VS Code ^1.86.0 per package.json engines.

Thanks for maintaining codesyncapp/codesync-vs!