spinframework/containerd-shim-spin

Output all triggers on app startup

Open

#226 opened on Nov 7, 2024

View on GitHub
 (0 comments) (3 reactions) (0 assignees)Rust (30 forks)auto 404
good first issue

Repository metrics

Stars
 (138 stars)
PR merge metrics
 (PR metrics pending)

Description

Right now, the shim only logs the HTTP endpoints available at startup. Ideally it would log information about other triggers that are available. Take for example an app that has 2 HTTP triggered components and 1 mqtt triggered component, the output is simply:

Serving http://0.0.0.0:80
Available Routes:
  api: http://0.0.0.0:80/api
  frontend: http://0.0.0.0:80 (wildcard)

It would be nice to also have information about the other triggers

Contributor guide

Research direction
Locate the code that currently logs HTTP routes on startup (likely in the shim's main or initialization). Examine how triggers are stored and iterate over all trigger types to log their details similarly.
Tech stack
rust
Domain
backenddevops
Issue type
Feature
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustcontainerd shim spin internals
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40