ashupednekar / ashupednekar/litefunctions
governance (RBAC, audit trail, policy guardrails)
- Dominant language
- Go
- Stars
- 5
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
Introduce governance controls for multi-user and multi-tenant operation.
## Motivation
As adoption grows, operational safety requires RBAC, policy controls, and auditability.
## Proposal
- Org/project-level RBAC model.
- Audit logs for function/config/deploy/invoke admin actions.
- Policy guardrails (OPA/Kyverno-compatible) for unsafe configs.
- Approval workflows for production-impacting changes.
## Acceptance criteria
- Role model is documented and enforced by API.
- Audit events are emitted for critical actions.
- Policy engine can block disallowed runtime/deploy configs.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue does not name files, tests, or entry points. Start by mapping the API paths and runtime/deploy configuration handling, then determine where roles, audit events, policy evaluation, and approvals belong. Done means documented and enforced roles, critical-action audit events, and policy checks that block disallowed configurations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100