Deployment API requires global deployment ID instead of project specific deployment ID

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

• Close this issue

Problem

We have Deployment APIs to fetch deployment information in a specific project. And, some of the API requires deployment_id as a parameter. For example, List of merge requests associated with a deployment API requires deployment_id in the query param:

GET /projects/:id/deployments/:deployment_id/merge_requests

This deployment_id refers the primary key of the database records, and more importantly, this ID is NOT surfaced on UI. For example,

You see Deployment #2 and #3 in the UI. These are project specific deployment IDs (a.k.a. IID - Internal ID), which is sequential number per project. This confuses users that they're trying to fetch the data with GET /projects/:id/deployments/3/merge_requests that returns no information.

Workaround

• Find a target deployment via List project deployments API
• Parse id from the JSON resopnse.

Proposal

We should support deployment_iid by default, instead of deployment_id.