and running local dev server with "aio app run --local" I get the following error message:
OpenWhiskError: POST http://localhost:3233/api/v1/namespaces/whisk.system/actions/alarms/interval?blocking=true Returned HTTP 403 (Forbidden) --> "The supplied authentication is not authorized to access 'whisk.system/alarms'."
Question 1: what do I need to change to get proper authentication?
on the other hand, it runs leaving out the "--local" parameter with the following message:
Local Dev Serverinterval:0ebaeb2b80054388baeb2b800523887b
so it looks as the trigger has successfully been placed on whisk with the desired interval.
but as soon as the trigger reaches the interval, the following error message appears in console:
Hi @ursboller, here are answers relevant to your questions.
Answer 1: It is not possible to deploy an alarmed trigger in `--local` mode, because the alarms provider and packages are not deployed in your local openwhisk. You have to deploy it on I/O Runtime (without `--local`).
Answer 2: I tried the same setup as yours and it seems to work for me. The only difference is, I set the `require-adobe-auth` flag to false and removed `web: yes`, because the alarm is not able to provider a token as a web request. That way the action is still secure and can only be triggered by the alarm, not an external entity.