What is the feature?
Users of a project are not always the same person who implemented it. When pipeline and other config values are being replaced and there is a value being replaced, ie: the new config structure has been defined alongside the old config structure, there should be a warning raised to ensure users know the replacement may have removed configuration.
Any other context?
Example: data.test.pipeline is defined but test_pipeline also exists in the file due to migration.
If conpat_config is used, the data.test.pipeline value is replaced because the test_pipeline exists. A new user would assume the data.test.pipeline is the newer configuration structure and is likely the source of pipeline configuration unless they inspect deeper into code.
What is the feature?
Users of a project are not always the same person who implemented it. When pipeline and other config values are being replaced and there is a value being replaced, ie: the new config structure has been defined alongside the old config structure, there should be a warning raised to ensure users know the replacement may have removed configuration.
Any other context?
Example: data.test.pipeline is defined but test_pipeline also exists in the file due to migration.
If conpat_config is used, the data.test.pipeline value is replaced because the test_pipeline exists. A new user would assume the data.test.pipeline is the newer configuration structure and is likely the source of pipeline configuration unless they inspect deeper into code.