Flagsmith / Flagsmith/flagsmith

Refactor feature change webhook into a proper audit-log based integration

Open
#5,629 1 comment 0 reactions 0 assignees View on GitHub
tech-debt
Dominant language
Python
Stars
6.6k
Forks
567
Avg merge
1d 13h
Merged PRs (30d)
121

Description

### Is your feature request related to a problem?

**Context**
*Feature change webhooks* are events sent to environment webhooks and have a path and implementation on their own.

We also have *audit webhooks* that are subscribed to all audit log envents at the organisation level.

Some integrations are audit-log based and operate at project level, which include:
- DataDog
- Dynatrace
- Grafana
- New Relic
- Sentry Change Tracking
- Slack
and organisation-level integrations that are also audit log based and sharing the same code paths.

The "audit log webhook" is currently neither and has a custom implementation.

All of this could lead to duplication of code execution.

**Investigation**
Inventorize and estimate the possibility to refactor feature change audit/environment log into a proper audit log based integration

### Describe the solution you'd like.

Webhook event triggering should be AuditLog based. The recording of a new AuditLog should be the entrypoint of sending environment-level webhook events

### Describe alternatives you've considered

TBD

### Additional context

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.