[BUG] Adding attribute 'description' limits fields returned to only those in attributes but doesn't include 'description' about manageiq-api HOT 9 CLOSED

That is the correct behavior, if you ask for specific attributes you’d just get those. It could be that description is nil thus not returned. If you get the VM with no attributes specified is description returned ?

from manageiq-api.

@abellotti ah yes, you're right description is NULL in the database.

I would expect that this would be returned and just set to null in the JSON object?

Otherwise, when i get the object back and try to access it response["resources"][0]["description"] that field doesn't exist.

from manageiq-api.

That is not the current behavior, by design. lotsa fields in some of those models. One option is for you to default above attribute access to null if not there.

from manageiq-api.

@abellotti Wait what? That's really confusing without context as the API semantics in this response are telling me "I am not returning you the description" instead of a nil value to indicate...well, that the description is nil; what's the reasoning for us wanting to have that designed behavior, then?

from manageiq-api.

since early days we don't return nil values, that was for minimizing payloads. The confusion here because the client asked for the particular attribute (via attributes=...) and they don't see it. From a semantics perspective, bug is that we should return it because they asked for it correct ?

from manageiq-api.

Yes; as discussed in Gitter, let's go ahead and remove all this functionality around omitting attributes if nil and relying on nil'ing and removing encrypted attrs.

from manageiq-api.

I am closing this issue as it was resolved by #253

from manageiq-api.

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

from manageiq-api.

@miq-bot close_issue

from manageiq-api.