>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567649. --> Reported by: [marcus_johansson](https://www.drupal.org/user/385947) Related to !1103 >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong>[One-line issue summary for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We have a provider in Amazee that can actually be setup without an API key now that they are allowing for anonymous accounts.</p> <p>The problem is that the current config action does not allow for you to setup a provider unless it requires a Key.</p> <p>This issue is as much feature as it is a bug, but since we can't guarantee 1.3.x being out before Drupal CMS, we add it to 1.2.x as well.</p> <h4 id="summary-steps-reproduce">Steps to reproduce (required for bugs, but not feature requests)</h4> <p>Try to use the config action without a key - it won't install default providers.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>1. Add a key to the value array in config action called <code>no_key_needed</code><br> 2. If this is explicitly set to true, we skip checking if an api key value is set and set the default models.<br> 3. If its not set or set to false, it just work as it currently does.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3>