- Issue created by @marcus_johansson
One issue right now on the places where we can freely test out stuff is that there might be a limit on how much money you can spend, or there might be services that the companies behind these are not allowed to share.
So, you might have some cool profile/mix of recipes that you want to show case, but this requires Unstructured or SERP API or its an expensive task that might have a one time cost of $5 etc.
We need a solution where you can spin up a machine, but as soon as you login on that machine, you should be forced to add an API key.
Create a module where you can setup via configuration which API key to fill out for which config and make sure that as soon as that configuration is not set, that all requests by a users that has access to change the API key, is being forwarded to the same form, unless the route is the submit or log out.
Also add to the configuration that the administrator/recipe creator can write a HTML message to explain why this has to be filled in.
Also create a configuration to be able to set forward route after the submit is sucessful.
This creates an user experience, where you start a demo product on something like DrupalForge or ddev, you login and you will be forced to add an API key before you can start using it.
This should be added outside of the scope of the AI module and be researched if something similar already exists or if its easy to solve in ECA.
Active
Ideas