- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Hi @Urs_Boller.
Yes that's right, without `web: yes` your action can only be invoked by a trigger or directly by you in command line (aio runtime action invoke). Not possible to trigger from outside. IMO it makes sense from a security perspective, because you are assured that there is only one entry point per entity.
From the other thread I understand that you want to expose the same action functionalities to the UI as well. I would propose to create a (npm) library for the common methods of the shared functionalities. Because the authentication is not the same for headless (alarm-based) app and SPA (UI-based), you would need 2 apps in that case. So the action in the headless app doesn't have web exposure and is only triggered by alarm. On the other hand, the action in the SPA has web exposure and require-adobe-auth turned on so that it's only accessible by authorized users.
I'm not aware of a way to disregard the alarms set up in development mode. But that could be a good enhancement for the Firefly tooling. Do you mind creating a new issue in our CLI app plugin for this enhancement request? https://github.com/adobe/aio-cli-plugin-app
Views
Replies
Total Likes