changing the action associated with a privilege will cause bootstrap to terminate rather than replacing the privilege

[dmcassel]

Seen by @kford-oconnors. Copied problem description from #261, which was closed.

If you run bootstrap more than once with a URI privilege definition then it will complain on the second and subsequent attempts that the URI privilege already exists.(

ERROR: [{"qid":null, "type":"string", "result":"Configured privilege conflicts with existing one: name=cedent-269-role-uri; action=/data/hrlh/cedent-269; kind=uri (PRIV-MISMATCH):\nSee MarkLogic Server error log for more details."}]

Is there something different about setting up a URI privilege? Ideally I would like to set up lots of roles and URI privileges over time. I definitely want to stick with the Roxy deployer and not have to script this bit separately… any insights for me on how/why Roxy does this?

<privilege>
  <privilege-name>@ml.cedent1-role-uri</privilege-name>
  <action>/data/hrlh/@ml.cedent1-user</action>
  <kind>uri</kind>
  <role-ids>
    <role-id>@ml.cedent1-role</role-id>
    <role-id>@ml.hr-role</role-id>
  </role-ids>
</privilege>

[dmcassel]

fixed in dev