EventGate Read Stats Lambda - no auth yet

Open Beginner friendly
#200 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
aws, python
Domain
api, security

Research direction

Read event_gate_lambda.py first to follow the existing authorization pattern. Then inspect handler_stats.py and event_stats_lambda.py to apply the same auth check to the stats endpoint and decide if the separate handler should stay separate. Completion looks like protected access for stats requests and matching auth behavior to the other lambda handler.

Written by the indexing model from the issue text.

Description

enhancement
Feature Description

The event_stats_lambda.py has a separate handler and that does not implement auth.

Challenge whether a separated handler, by which I mean file handler_stats.py, is worth it, and if yes, add authorization as it is done in the other handler.

Problem / Opportunity

We need to protect this endpoint as it queries the real DB.

Acceptance Criteria

Endpoint is protected with authorization mechanism similar to the other lambda in event_gate_lambda.py

Dominant language
Python
Stars
4
Forks
0
Avg merge
20h 22m
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AbsaOSS/EventGate

All issues in AbsaOSS/EventGate

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.