Consider the scenario where you create a new Remote Config parameter in your template.json file and deploy it via the Firebase CLI to TEST and PROD environments with a default value. You then modify the value in PROD via the Firebase console. The next time you deploy Remote Config to PROD the value is overwritten. It would be useful for CI/CD deployments to have an option that would only deploy new parameters and would NOT overwrite the values for existing parameters. This would allow you to structure your template.json file to have default values for new non-PROD environments without having to always update the template.json values to match current PROD values before each deploy.