No, you can't revert drush cim without a backup (or alternate config export) of some sort. If you don't have a backup, you're out of luck.
One safety measure to prevent this kind of problem is to write a script that backs up your database and then calls drush cim. Then, only run the script to do a config import, and you can ensure you have always made a ...
Even though I never was able to figure out where the old D8 project config was coming from, I was able to resolve the problem by explicitly overriding the config at the very end of settings.php:
// Replace Acquia Dev Desktop settings (deprecated) with Acquia Cloud environment overrides.
// Note: This is for troubleshooting only; remove this code after ...
The correct way to handle this would be to write a hook_update_n() function and write the code out that would add those new config keys.
Then you would run drush updb and it would be added to the website.
The other answer is correct as well. I use both together and we can track everything in GIT from dev > stage > prod in case there are changes.
The simple answer for this issue is, with your idea search for the missed configuration.
for example in
Configuration core.entity_form_display.node.tool.default depends on the field.field.node.tool.field_sha256sum configuration that will not exist after import.
search for field.field.node.tool.field_sha256sum on your idea and remove them from the ...