Functionality

[cw00dw0rd]

Currently, the service creates a db, user, and password.
What further features are required?

[cw00dw0rd]

@joerg84 @rajivsam

[joerg84]

IMO we should include the hostname and port in the API. Just to be able to later return instances in another cluster without any API changes.

[cw00dw0rd]

Ok I will investigate returning hostname and port, I believe this should not be a problem.

[rajivsam]

@cw00dw0rd @joerg84 I think having the db_name, user_name, and password as parameters with defaults being empty is useful if the organization has a preference for particular values of the db_name, user_name, and password. I think having either:

1. One api, as we have now, with defaults being empty values for these parameters, and then creating the database with either the preferred values (provided by the client) or random values if nothing is provided.
2. A separate api for random and preferred database connection strings.