Heads up about plugins with Config Parameters: when you run the migration script, the generated JS migration file will include those plugin parameters.
If you want to keep the same plugin across environments but use different parameter configurations, note that the migration will overwrite the target environment’s parameters with those from the source/origin environment.
Could we have an option to NOT sync the config parameters?
Thanks!
Adding more context:
When working with plugins, we can store configuration parameters, which is really useful.
However, I’ve run into an issue when managing multiple environments and using the migration script via @datocms/cli.For example:
In the dev environment: SITE_URL=https://dev.mysite.com
In the test environment: SITE_URL=https://test.mysite.com
When I generate a migration from dev to test, the migration detects the SITE_URL value as a change and ends up overwriting the test environment setting with the dev value (https://dev.mysite.com).
This makes it difficult to keep environment-specific plugin settings without migrations unintentionally overriding them.Is there any option to ignore plugin parameter values when generating migrations (or to exclude specific parameters), so environment-specific settings aren’t treated as changes