Hello Stuart,
That does seem to do the trick. Thank you!
-Mike
On 08/28/2014 10:47 AM, stuart.mcla...@hp.com wrote:
Hi Mike,
Does it work if you put this at the very bottom of the file?
[.*]
create = @
read = @
update = @
delete = @
-Stuart
On Thu, 28 Aug 2014, Michael Turek wrote:
Hello,
I was wondering if the following behavior that I'm seeing with
protected properties is intended.
My setup is a ubuntu guest running devstack.
with the following protections file:
[admin]
create = admin
read = admin
update = admin
delete = admin
[protected]
create = test
read = test
update = test
delete = test
The following command fails to add a property:
$# glance --os-username admin image-update --property x=True
<image-name-here>
Request returned failure status 403.
<html>
<head>
<title>403 Forbidden</title>
</head>
<body>
<h1>403 Forbidden</h1>
Property 'x' is protected<br /><br />
</body>
</html> (HTTP 403)
If the property is unspecified in the protections file, shouldn't
there be no restrictions on it? Any insight is appreciated, thanks!
-Mike
_______________________________________________
Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
