Hanish, I have added access to you to edit this page
https://cwiki.apache.org/confluence/display/RANGER/REST+APIs+for+Policy+Management

Please check and add in your changes

On Wed, Jan 28, 2015 at 11:45 PM, Hanish Bansal <[email protected]
> wrote:

>   ​
>  Hi Balaji,
>
>  I have filed JIRA for this @
> https://issues.apache.org/jira/brow​se/RANGER-231
> <https://issues.apache.org/jira/browse/RANGER-231>
> ​
>  Request you to  give wiki write access
>
>
>       -------
>
> *Thanks & Regards, Hanish Bansal*
> Software Engineer, iLabs
> Impetus Infotech Pvt. Ltd.
>      ------------------------------
> *From:* Balaji Ganesan <[email protected]>
> *Sent:* Thursday, January 29, 2015 7:24 AM
> *To:* [email protected]
> *Subject:* Re: Wiki Documentation of Update policy
>
>  Hanish, can you open a JIRA on this? I can give you permission to edit
> the Wiki page..
>
>   From: Hanish Bansal <[email protected]>
> Reply-To: "[email protected]" <
> [email protected]>
> Date: Wednesday, January 28, 2015 at 12:02 AM
> To: "[email protected]" <[email protected]>
> Subject: Wiki Documentation of Update policy
>
>    Hi,
>
>
>  I was using public rest api to update the policy (Request URL:
> *service/api/public/policy *). Refering to the wiki documentation for the
> same, i was getting 400 bad request error. Deep digging the api
> implementation, i found that repositoryName, repositoryType, id parameters
> are also required as request parameters.
>
>
>  Please let me know the expected behavior.
>
>
>  I would like to suggest that since this api is used to perform update
> operation by specified id so these parameters should not be required.
>
>
>  If these additional parameters (repositoryName, repositoryType, id ) are
> mandatory for this api, then the documentation need to be updated
> accordingly.
>
>      -------
>
> *Thanks & Regards, Hanish Bansal*
> Software Engineer, iLabs
> Impetus Infotech Pvt. Ltd.
>
> ------------------------------
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity
> to which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
> ------------------------------
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential,
> proprietary, privileged or otherwise protected by law. The message is
> intended solely for the named addressee. If received in error, please
> destroy and notify the sender. Any use of this email is prohibited when
> received in error. Impetus does not represent, warrant and/or guarantee,
> that the integrity of this communication has been maintained nor that the
> communication is free of errors, virus, interception or interference.
>

Reply via email to