Difference between revisions of "Trove/update-instance-name"
< Trove
Iccha-sethi (talk | contribs) (→Augment existing API call: Update Database Instance) |
|||
| Line 20: | Line 20: | ||
The PATCH call does following functions: | The PATCH call does following functions: | ||
(1) updates configuration by doing the necessary checks (same as PUT call) | (1) updates configuration by doing the necessary checks (same as PUT call) | ||
| − | and/or | + | and/or (If the config is None, the config group is dropped.) |
(2) updates instance name if provided | (2) updates instance name if provided | ||
Revision as of 19:44, 21 August 2014
Contents
Description
This blueprint adds PATCH /instances/{instanceId} call for renaming an instance name/attaching or detaching a configuration to an instance. The long term plan is to deprecate the PUT /instances/{instanceId} call.
Blueprint: https://blueprints.launchpad.net/trove/+spec/update-instance-name
Justification/Benefits
Need to provide users ability to rename a database instance name post creation.
Impacts
Configuration
None
Database
No impact
ReST API
Augment existing API call: Update Database Instance
The PATCH call does following functions: (1) updates configuration by doing the necessary checks (same as PUT call) and/or (If the config is None, the config group is dropped.) (2) updates instance name if provided
Request
PATCH {tenantId}/instances/{instanceId}
{
"instance": {
"configuration" : "StagingConfig",
"name" : "Test_Instance"
}
}
Response
This call will not return a response body.
