Promote and deprecate part of the API

Registered by Denis M.

Trove now has two parts of the API:

Core part:
    Instance API.
    Backup API.
    Datastores API.
    Configuration API.
Extension API:
    MySQL users API.
    MySQL schemas API.
    MySQL user ACL API.
    Security groups API.
    Mgmt API.
        Hosts API.
        Instances API.
        Quotas API.
        Volumes API;
    Accounts API.

I’d like to propose to start the discussion related to API changes(promotion and deprecation). Here’s the actual plan with steps, that doesn’t break API backward compatibility:

Promote Security Groups API from Extension to Core API.
Promote Quotas API from Extension to Core API.
(Probably) Promote all Mgmt API from Extension to Core API.

Approach for the promotion. Operations like provisioning, backuping are running with quotas by the default, so it looks like the straight point for the promotion.

And, of course, there’s the part of the Extensions API that should be deprecated in favor of the project definition (pure DBaaS):
Deprecate Extension API related to the MySQL (users API, schemas API, ACL API).

    Approach for the deprecation of the extension API. Given API is not flexible from the other datastore types perspective. From the perspective of the side tools like well-written database clients/connectors no need to override already implemented features.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Denis M.
Direction:
Needs approval
Assignee:
None
Definition:
Obsolete
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Denis M.

Related branches

Sprints

Whiteboard

[SlickNik] Please follow BP template if approval is needed. Thanks!

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.