You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Its odd that it includes DeploymentProcessId, but not a link to it.
You can get to it by going to the Release link, and then the ProjectDeploymentProcessSnapshot link, but its a bit of a pain (side note, its called ProjectDeploymentProcessSnapshotId on the releases object, not DeploymentProcessId, which is a bit interesting.)
I propose we add a DeploymentProcess link to the deployment api response.
The text was updated successfully, but these errors were encountered:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 23, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Calling
/api/deployments/Deployments-6878
returns:Its odd that it includes
DeploymentProcessId
, but not a link to it.You can get to it by going to the
Release
link, and then theProjectDeploymentProcessSnapshot
link, but its a bit of a pain (side note, its calledProjectDeploymentProcessSnapshotId
on the releases object, notDeploymentProcessId
, which is a bit interesting.)I propose we add a
DeploymentProcess
link to the deployment api response.The text was updated successfully, but these errors were encountered: