[
https://issues.apache.org/jira/browse/JCLOUDS-691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14159669#comment-14159669
]
Adrian Cole commented on JCLOUDS-691:
-------------------------------------
wrt best practices, a fallback on resource not found is only appropriate for a
GET, HEAD, or DELETE, we indeed should document that, if not aim to eventually
compile-time enforce this.
> The 404 fallbacks should be removed from PUT and POST operations in the
> OpenStack APIs
> --------------------------------------------------------------------------------------
>
> Key: JCLOUDS-691
> URL: https://issues.apache.org/jira/browse/JCLOUDS-691
> Project: jclouds
> Issue Type: Bug
> Components: jclouds-compute, jclouds-labs-openstack
> Affects Versions: 1.8.0
> Reporter: Ignasi Barrera
> Assignee: Ignasi Barrera
> Labels: openstack, rackspace
> Fix For: 2.0.0
>
>
> Write operations such as PUT or POST should not use the 404 fallbacks that
> silently return null instead of propagating an exception. The fallback should
> be removed so a ResourceNotFoundException is propagated.
> See the discussion here:
> https://github.com/jclouds/jclouds-labs-openstack/pull/135/files#r16700137
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
