GitHub user yanboliang opened a pull request:
https://github.com/apache/zeppelin/pull/2621
[Minor] Remove hardcoded key in zeppelinhub.
### What is this PR for?
Hardcoded key may cause security issue, so remove the potential risk.
### What type of PR is it?
[Improvement]
### Todos
* [ ] - Task
### What is the Jira issue?
No jira created.
### How should this be tested?
* First time? Setup Travis CI as described on
https://zeppelin.apache.org/contribution/contributions.html#continuous-integration
* Strongly recommended: add automated unit tests for any new or changed
behavior
* Outline any manual steps to test the PR here.
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update?
* Is there breaking changes for older versions?
* Does this needs documentation?
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yanboliang/zeppelin key
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/zeppelin/pull/2621.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 #2621
----
commit 251528306c88d4bf435a9504d9437d0b830b4a68
Author: Yanbo Liang <yblia...@gmail.com>
Date: 2017-10-11T23:13:55Z
Remove hardcoded key in zeppelinhub.
----
---
