As of rev 904, the resource is correctly unimplemented. Here are the status codes I saw in my testing with trunk rev 940:
GET http://172.19.0.3:8774/v1.0/shared_ip_groups -> 501 GET http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501 POST http://172.19.0.3:8774/v1.0/shared_ip_groups -> 501 PUT http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501 DELETE http://172.19.0.3:8774/v1.0/shared_ip_groups/1 -> 501
FYI, the resource is removed as of v1.1, so we see 404s across the board now:
GET http://172.19.0.3:8774/v1.1/shared_ip_groups -> 404 GET http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404 POST http://172.19.0.3:8774/v1.1/shared_ip_groups -> 404 PUT http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404 DELETE http://172.19.0.3:8774/v1.1/shared_ip_groups/1 -> 404
Kevin, if you believe this is correct, we can resolve this bug.
As of rev 904, the resource is correctly unimplemented. Here are the status codes I saw in my testing with trunk rev 940:
GET http:// 172.19. 0.3:8774/ v1.0/shared_ ip_groups -> 501 172.19. 0.3:8774/ v1.0/shared_ ip_groups/ 1 -> 501 172.19. 0.3:8774/ v1.0/shared_ ip_groups -> 501 172.19. 0.3:8774/ v1.0/shared_ ip_groups/ 1 -> 501 172.19. 0.3:8774/ v1.0/shared_ ip_groups/ 1 -> 501
GET http://
POST http://
PUT http://
DELETE http://
FYI, the resource is removed as of v1.1, so we see 404s across the board now:
GET http:// 172.19. 0.3:8774/ v1.1/shared_ ip_groups -> 404 172.19. 0.3:8774/ v1.1/shared_ ip_groups/ 1 -> 404 172.19. 0.3:8774/ v1.1/shared_ ip_groups -> 404 172.19. 0.3:8774/ v1.1/shared_ ip_groups/ 1 -> 404 172.19. 0.3:8774/ v1.1/shared_ ip_groups/ 1 -> 404
GET http://
POST http://
PUT http://
DELETE http://
Kevin, if you believe this is correct, we can resolve this bug.