Actions
User story #3952
closedManage Change Request through REST API
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
As other parts of the webapp, we need to be able to act on change request through the API.
Functions needed :
- List change requests /api/changeRequests- parameters : state of change requests to see
- individual states : Pending Validation, Pending Deployment, Deployed, Cancelled
- multiple states : Open (Pending ...), Close (the other), All
- Default Value : Open => like when you look at change requests page
- See a change request Detail : /api/changeRequests/id
- no parameters
- display possible actions.
- Accept it :
- parameters : action, deploy immediatly or send to pending deploy
- Decline it
-( no parameters
Updated by Nicolas PERRON about 11 years ago
- Status changed from 13 to Pending release
Updated by Vincent MEMBRÉ about 11 years ago
- Subject changed from Handle change request through API to Manage Change Request through REST API
Updated by Vincent MEMBRÉ about 11 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.8.0~beta1, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-October/000056.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog28
- Download information: http://www.rudder-project.org/foswiki/Download/
Actions