apache / apache/openwhisk

Triggers should activate actions via internal interface

Open
#2,614 0 comments 0 reactions 0 assignees View on GitHub
controller help wanted
Dominant language
Scala
Stars
6.8k
Forks
1.2k
Avg merge
2d 14h
Merged PRs (30d)
2

Description

Currently a trigger causes an action activation through an external interface - but we should use an internal interface.

- [ ] refactor entitlement check to authorize action
- [ ] create internal interface for activation a trigger (useful to surface web triggers)
- [ ] replace http post request for internal interface
- [ ] restoring ability to track causality

Also consider as part of this some long needed changes to handing of triggers:
- [ ] persistence of trigger and/or rule activations https://github.com/apache/incubator-openwhisk/issues/512
- [ ] logging activation ids (or failures)

Contributor guide

Open the contributing guide

Research direction

Start with the issue checklist and the linked issue #512, then trace the existing trigger-to-action activation path in the OpenWhisk codebase. Done means the listed interface, authorization, HTTP replacement, causality, persistence, and activation logging concerns are resolved or explicitly scoped.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
api, backend, distributed-systems
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.