Warn or block apex code run or metadata deployments to production instance from VS Code

[kiran-machhewar]

As a Salesforce developer, it's common to connect to both sandboxes and production environments using the Salesforce CLI. Production connection is primarily for SOQL builder and running adhoc apex scripts. While features like the SOQL builder and running Apex code from the VS Code Salesforce extension are powerful, there's a risk of accidentally deploying metadata or running ad-hoc Apex in a production org. This can lead to serious issues.

To prevent this, it would be a valuable addition to the Salesforce VS Code extension to have an optional setting that warns or blocks a deployment to a production org. This would provide a safety net, alerting a developer who might have forgotten they were connected to production and preventing unintended consequences.