Include Pipeline Inputs in Pipeline Webhook Events / Rest API

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Release notes

Problem to solve

Add support for exposing pipeline input parameters in pipeline webhook event payloads (currently hidden) / Pipeline REST API, so that external systems and integrations can use this data when processing pipeline events. 

Intended users

• External Services Administrators

Usecase

Disaster Recovery/Missed webhook events by external service

External Services Administrators want to know the inputs that were used to trigger the GitLab CI pipeline so that the external system (receiving the webhooks) could retrigger the same pipeline (with same inputs) if necessary.

User experience goal

The user should be able to fetch Pipeline inputs runtime values.

Proposal

Further details

Permissions and Security

• Add expected impact to Maintainer (40) members
• Add expected impact to Owner (50) members

Documentation

Availability & Testing

Available Tier

• Free
• Premium
• Ultimate

Feature Usage Metrics

What does success look like, and how can we measure that?

To have this feature implemented.

What is the type of buyer?

Is this a cross-stage feature?

Yes

What is the competitive advantage or differentiation for this feature?

Links / references