GitHub user AhyoungRyu opened a pull request:
https://github.com/apache/zeppelin/pull/1825
[DOCS][ZEPPELIN-1586] Add 'Security' section under notebook restapi docs
### What is this PR for?
After #1567 merged we can get/set note permission information for a certain
note. But this info is not described in anywhere. So I added "Security" section
under
[docs/rest-api/rest-notebook.md](https://github.com/apache/zeppelin/blob/master/docs/rest-api/rest-notebook.md).
And currently so many operations are placed under one section like below.
<img
src="https://cloud.githubusercontent.com/assets/10060731/21560964/c55d41cc-cea9-11e6-96ac-68f762c68bff.png"
width="400px">
So I split them under each `Note opersions`, `Paragraph operations`, `Cron
jobs`, and `Security`.
<img
src="https://cloud.githubusercontent.com/assets/10060731/21560971/cd57cf46-cea9-11e6-9a41-95c817594c9c.png"
width="400px">
### What type of PR is it?
Documentation
### What is the Jira issue?
[ZEPPELIN-1877](https://issues.apache.org/jira/browse/ZEPPELIN-1877)
### How should this be tested?
Please see the below screenshots :)
### Screenshots (if appropriate)



### Questions:
* Does the licenses files need update? no
* Is there breaking changes for older versions? no
* Does this needs documentation? no
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/AhyoungRyu/zeppelin ZEPPELIN-1586/docs
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/1825.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1825
----
commit 09d22d30ff8f927a5754c9c6f0f74ffb28ef8a71
Author: AhyoungRyu <[email protected]>
Date: 2016-12-30T06:59:20Z
Add 'Security' section under notebook restapi docs
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---