Jump to: navigation, search

Difference between revisions of "Trove/update-instance-name"

m (Augment existing API call: Update Database Instance)
m (Description)
Line 1: Line 1:
 
== Description ==
 
== Description ==
  
This blueprint will augment the existing API PUT/instances/{instanceId} call for renaming an instance name.
+
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
 
Blueprint: https://blueprints.launchpad.net/trove/+spec/update-instance-name

Revision as of 21:39, 7 May 2014

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

Request

PATCH {tenantId}/instances/{instanceId}

{
"instance": {
"configuration" : "StagingConfig",
"name" : "Test_Instance"
}
}

Response

This call will not return a response body.

Comments/Questions From Community