Whenever new content is added this module adds data in the thrid_party_settings of the content type. If the config is managed by a version control system then the config will need to be committed _every time new content is created_. I would argue that this data should be considered as content, rather than config, and stored in the database instead.
Create a custom database table
Store and access Entity Redirect data in this custom database table
N/A
TBC
TBC
Postponed: needs info
2.0
Code
It should only be per content type not per content. What steps can replicate this? (I wasn't able to with the above steps)