Christian Karnath created DTACLOUD-418:
------------------------------------------
Summary: Missing href-attribute in JSON output
Key: DTACLOUD-418
URL: https://issues.apache.org/jira/browse/DTACLOUD-418
Project: DeltaCloud
Issue Type: Bug
Components: Native/Frontend
Environment: Debian 6.0.6, ruby 1.9.2p0, deltacloud development
Reporter: Christian Karnath
The 'href' attribute was present in Deltacloud 1.0.2 but it is missing in the
current development version when specifying JSON as an output format:
Requesting /api/instances against deltacloud 1.0.2 returned:
{
"instances": {
"instance": {
"name": null,
"owner_id": "mockuser",
"image": { … },
"realm": { … },
"state": "RUNNING",
"hardware_profile": { … },
"actions": { … },
"public_addresses": { … },
"private_addresses": { … },
"storage_volumes": null,
"authentication": { … },
"href": "https://192.168.23.101:3001/api/instances/inst0";,
"id": "inst0"
}
}
}
Requesting /api/instances against deltacloud development version returns:
{
"instances": [
{
"id": "inst1",
"name": "MockUserInstance",
"state": "RUNNING",
"owner": "mockuser",
"image": { … },
"realm": { … },
"actions": [ … ],
"instance_profile": { … },
"public_addresses": [ … ],
"private_addresses": [ … ],
"launch_time": null,
"create_image": true,
"storage_volumes": [ ]
}
]
}
It seems that /api/images, /api/realms and so on are also inconsistent with the
corresponding xml representation (which includes the 'href'-attribute).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
