Allow custom HTTP headers with streaming audit events
Release notes
Problem to solve
Users want to add custom HTTP headers to their streaming audit events so that the receiving applications can correctly identify and process them.
Proposal
Allow users to add custom headers to HTTP streaming audit event destinations. Allow this to be done from the API as well as from the UI.
- Refinement note: Can the API be used to implement the UI, rather than building two approaches?
New APIs should be introduced to:
- Listing all custom HTTP headers for a given streaming audit event destination
- Adding a custom HTTP header as a key/value pair for a given streaming audit event destination
- Ability to disable a custom HTTP header
- Removing an existing custom header for a given streaming audit event destination
- Thought: Should likely use the
gid://
object in APIs
Update the create new streaming audit event destination API to:
- Allow one or more custom HTTP headers to be defined as an optional parameter
Design
Older Conceptual UX
Intended users
Feature Usage Metrics
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.