apache/openwhisk

Triggers should activate actions via internal interface

Open

#2,614 opened on Aug 13, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (1,177 forks)batch import
controllerhelp wanted

Repository metrics

Stars
 (6,777 stars)
PR merge metrics
 (Avg merge 17h 31m) (3 merged PRs in 30d)

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:

Contributor guide

Research direction
Study the current trigger activation flow in OpenWhisk, focusing on how triggers activate actions via HTTP post. Identify where the external interface is used and how to replace it with an internal interface. Look for existing internal interfaces in the codebase, such as those used for web triggers. Understand the entitlement check for authorization and how to refactor it. Trace the causality tracking mechanism. Review related issues for persistence and logging.
Tech stack
scala
Domain
backendapi
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaGitOpenWhisk concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60