API docs incorrect for v2 spaces

[ScarletTanager]

Hi,

http://apidocs.cloudfoundry.org/245/spaces/update_a_space.html says that one can do a PUT on the space to change the organization guid - this is not AFAIK correct. It is probably worthwhile with the new flattened API docs to check that they are completely accurate.

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/133055661

The labels on this github issue will be updated when the story is started.

[luan]

Hi @ScarletTanager,

We addressed the documentation issue. The field is actually acceptable in that request, the issue is that the only valid value you can pass in is the guid of the currently associated org, and it will default to that.
This is not a particularly useful field to have in the API request, but it allows one to pass in the full space object back to the API, enabling for scripting and automation.

Thanks,
@luan & @ericpromislow, CF CAPI Team

[ScarletTanager]

@luan - what you say about passing in the complete object makes sense from a scripting/automation perspective - is it worth explaining why that is so in the docs? I'm fine either way, but seems like useful context. The commit looks good to me if you don't want to add that explanation, do you want to close the issue or should I?

[SocalNick]

I'd like to try to eliminate the 500 and instead return a 4xx with message like, The organization_guid field cannot be changed.

[SocalNick]

Documentation change and returning 400 will be in next CAPI-Release