Add audit logging for gateway configuration changes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Description
Add an audit log to the gateway that records all configuration changes — API deployments, undeployments, policy updates, and other mutations — along with the actor, timestamp, and operation details. This enables operators to audit what changed, when, and by whom.
Changes that should be captured include:
- API deploy / undeploy / update via the gateway-controller REST API
- Policy attachment or detachment
- Gateway configuration changes (auth config, TLS, uptime changes)
The audit log should be queryable (e.g. via a REST endpoint on gateway-controller) and persistent (survives restarts).
Version
No response
Related Issue
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the gateway-controller REST API and the configuration mutation paths named in the issue: deployments, policies, authentication, TLS, and uptime. Determine how audit records will be persisted, exposed for querying, and retained across restarts. Done means every listed mutation records its actor, timestamp, and operation details and the records can be queried after a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100