[
https://issues.apache.org/jira/browse/JCLOUDS-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13901196#comment-13901196
]
Ignasi Barrera commented on JCLOUDS-468:
The DigitalOcean provider also needs a b
Everett Toews created JCLOUDS-468:
-
Summary: Nova needs to handle key pair creation better in the
ComputeService
Key: JCLOUDS-468
URL: https://issues.apache.org/jira/browse/JCLOUDS-468
Project: jcloud
[jclouds-java-7-pull-requests
#1072](https://jclouds.ci.cloudbees.com/job/jclouds-java-7-pull-requests/1072/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290#issuecomment-35023639
[jclouds-pull-requests
#601](https://jclouds.ci.cloudbees.com/job/jclouds-pull-requests/601/) SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290#issuecomment-35023554
[jclouds ยป jclouds
#842](https://buildhive.cloudbees.com/job/jclouds/job/jclouds/842/) SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/290#issuecomment
> @@ -86,4 +88,37 @@ public void testUsersByName() {
>}
>
> }
> +
> + public void testAddDeleteUser() {
> + UserApi userApi = api.getUserApi().get();
> + Set initialUsers = userApi.list().concat().toSet();
> +
> + // generate credentials for a random new use
> @@ -86,4 +88,37 @@ public void testUsersByName() {
>}
>
> }
> +
> + public void testAddDeleteUser() {
> We should be able to figure out which operation failed by looking at which
> assert failed.
Sure, but if you're looking at test results in Jenkins or whatever, it's nice
> @@ -86,4 +88,37 @@ public void testUsersByName() {
>}
>
> }
> +
> + public void testAddDeleteUser() {
I wrote this as one test because the test for the delete operation requires
that the add operation succeed, and that we know the ID of the user that was
created.
We should
Fixed javadoc style comments.
I'm not particularly tied to the fallback behavior on user deletion; I'm open
to other options. Once we figure out what behavior we want, I'll update the
javadoc so that it better describes the behavior.
---
Reply to this email directly or view it on GitHub:
https:
> +
> + User newUser = userApi.add(randUser, email, true, password);
> +
> + // validate that our new user exists
> + Set newUsers = userApi.list().concat().toSet();
> + assertTrue(newUsers.contains(newUser));
> +
> + // validate that we can delete our use
> @@ -86,4 +88,37 @@ public void testUsersByName() {
>}
>
> }
> +
> + public void testAddDeleteUser() {
Split this out into two tests, one depending on the other? Like this, if the
test fails, we don't know which of the operations broke...
---
Reply to this email directly or v
> + @Path("/users")
> + @RequestFilters(AuthenticateRequest.class)
> + @Fallback(NullOnNotFoundOr404.class)
> + ListenableFuture add(@PayloadParam("username") String
> userName,
> +@PayloadParam("email") String
> userEmail,
> +
> @@ -81,4 +81,21 @@
> */
> Set listRolesOfUserOnTenant(String userId, String
> tenantId);
>
> + /**
> +* Create a new user in keystone.
"Creates" (per Javadoc style guide - descriptive over imperative)
---
Reply to this email directly or view it on GitHub:
https://github.com/jc
> @@ -81,4 +81,21 @@
> */
> Set listRolesOfUserOnTenant(String userId, String
> tenantId);
>
> + /**
> +* Create a new user in keystone.
> +*
> +* @param userName the name for the new user
> +* @param userEmail the email address for the new user
> +* @param enable
> I'll give it a go and test this with the master branch.
Thanks, @spark404!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/184#issuecomment-34985369
[
https://issues.apache.org/jira/browse/JCLOUDS-467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900119#comment-13900119
]
Ignasi Barrera commented on JCLOUDS-467:
Maybe just taking the nodeNames iterator
> @@ -123,4 +137,29 @@
> @Fallback(EmptySetOnNotFoundOr404.class)
> ListenableFuture>
> listRolesOfUserOnTenant(@PathParam("userId") String userId,
> @PathParam("tenantId") String tenantId);
> +
> + /**
> +* @see UserApi#add(String, String, Boolean, String)
> +*/
17 matches
Mail list logo