Add database API endpoints to retrieve the list of databases.

[DiscoPYF]

#29

[DiscoPYF]

I noticed that the properties in DeleteDatabaseResult and PostDatabaseResult do not conform with what is returned by ArangoDB. I left them as is in this PR and will create another issue to address that. Let me know if you think otherwise.

The examples listed in the specs:

Creating a database named example.

{ 
  "name" : "example" 
}
EOF

HTTP/1.1 Created
content-type: application/json; charset=utf-8
x-content-type-options: nosniff

{ 
  "error" : false, 
  "code" : 201, 
  "result" : true 
}

Creating a database named mydb with two users.

shell> curl -X POST --header 'accept: application/json' --data-binary @- --dump - http://localhost:8529/_api/database <<EOF
{ 
  "name" : "mydb", 
  "users" : [ 
    { 
      "username" : "admin", 
      "passwd" : "secret", 
      "active" : true 
    }, 
    { 
      "username" : "tester", 
      "passwd" : "test001", 
      "active" : false 
    } 
  ] 
}
EOF

HTTP/1.1 Created
content-type: application/json; charset=utf-8
x-content-type-options: nosniff

{ 
  "error" : false, 
  "code" : 201, 
  "result" : true 
}

[rossmills99]

Do we have tests yet for Create database?

[rossmills99]

I'll answer my own question - as far as I can tell, we haven't done the proper implementation for Create database yet so we shouldn't check it off in the task list yet. Can you uncheck it for now?

[DiscoPYF]

Yep I will do that.

[DiscoPYF]

While we do not have an explicit test for create database, most (if not all) the per-test-class fixtures use the method the create a test database.

[rossmills99]

Yes, the criteria for marking a task complete is that we have implemented both the endpoint and tests of the endpoint. Those methods existed for use in other tests but there are no tests explicitly for them yet.

[rossmills99]

I noticed that the properties in DeleteDatabaseResult and PostDatabaseResult do not conform with what is returned by ArangoDB. I left them as is in this PR and will create another issue to address that. Let me know if you think otherwise.

The examples listed in the specs:

Creating a database named example.

{ 
  "name" : "example" 
}
EOF

HTTP/1.1 Created
content-type: application/json; charset=utf-8
x-content-type-options: nosniff

{ 
  "error" : false, 
  "code" : 201, 
  "result" : true 
}

Creating a database named mydb with two users.

shell> curl -X POST --header 'accept: application/json' --data-binary @- --dump - http://localhost:8529/_api/database <<EOF
{ 
  "name" : "mydb", 
  "users" : [ 
    { 
      "username" : "admin", 
      "passwd" : "secret", 
      "active" : true 
    }, 
    { 
      "username" : "tester", 
      "passwd" : "test001", 
      "active" : false 
    } 
  ] 
}
EOF

HTTP/1.1 Created
content-type: application/json; charset=utf-8
x-content-type-options: nosniff

{ 
  "error" : false, 
  "code" : 201, 
  "result" : true 
}

Yes I agree. These have so far only been implemented to help with writing tests of the other endpoints, so they aren't considered "complete" yet. We should model the complete response from ArangoDB and that can be done as part of the "proper" implementation of those endpoints (i.e. when we come to implement tests for them and tick them off in our roadmap task list)

[DiscoPYF]

@rossmills99 Maybe this should be named GetDatabasesAsync?

[rossmills99]

Yes, I think I agree

[DiscoPYF]

Ok, I will create a new issue for that.