The AI recipe should do lenient comparison with existing config, to avoid breaking Project Browser
>>> [!note] Migrated issue
<!-- Drupal.org comment -->
<!-- Migrated from issue #3525114. -->
Reported by: [joachim namyslo](https://www.drupal.org/user/275771)
Related to !546
>>>
<h3 id="summary-problem-motivation">Problem/Motivation</h3>
<p>I have activated the recipe AI Drupal Assistant and used an API from Open AI by Chat GPT. Unfortunately, once the recipe is activated, I can't activate any more recipes because the list of recipes on the Expand page in the Recommend tab is simply empty afterwards. The reason for this is the following error message:</p>
<blockquote><p>Drupal\Core\Recipe\RecipePreExistingConfigException: The configuration 'image.style.ai_image_alt_text' exists already and does not match the recipe's configuration in Drupal\Core\Recipe\ConfigConfigurator->__construct() (line 62 of /var/www/cms/web/core/lib/Drupal/Core/Recipe/ConfigConfigurator.php).
</p></blockquote>
<p>I can't say why this is the case. I also have no idea why an image style that already exists suddenly means that the list of recipes available for installation no longer exists. That makes no sense to me at all, but unfortunately, it is a fact. I have just tested this again on a fresh Drupal installation because I was afraid that the bug could not be reproduced. But I was wrong, it's very easy to reproduce this bug. If anyone has a patch for it, I would be grateful. Otherwise, I'll have to start again with a fresh Drupl CMS installation.</p>
<p><img src="https://www.drupal.org/files/issues/2025-05-18/18-05-2025_00-53-23.png" width="100%" height="100%" alt="Recieps gone after AI Chatbot Assistant Recipe was enabled"></p>
<h4 id="summary-steps-reproduce">Steps to reproduce</h4>
<p>Install Drupal CMS as usual<br>
Go to /admin/modules/browse/recipes<br>
Enable the Chatbot AI recipe<br>
Enter an API key<br>
Let it finish the install process<br>
Now you can see all recieps are gone, becuase tey could not be loaded anymore.</p>
<h3 id="summary-proposed-resolution">Proposed resolution</h3>
<h3 id="summary-ui-changes">User interface changes</h3>
<p>find the root cause<br>
write a patch<br>
apply patch<br>
re-release the recipe</p>
<h3 id="summary-data-model-changes">Configuration changes</h3>
<p>TBD</p>
issue