Of we go: https://github.com/apache/zeppelin/pull/2599 :-)
h
On Mon, Sep 25, 2017 at 12:06 PM, moon soo Lee wrote:
> Sounds like a plan!
>
> On Mon, Sep 25, 2017 at 11:33 AM Herval Freire
> wrote:
>
>> I started something on that direction here, for internal use:
>> https://github.com/herval/z
Sounds like a plan!
On Mon, Sep 25, 2017 at 11:33 AM Herval Freire wrote:
> I started something on that direction here, for internal use:
> https://github.com/herval/zeppelin/tree/encrypt-credentials
>
> If that's the kind of thing that may interest everyone else, I can get a
> PR going
>
> h
>
I started something on that direction here, for internal use:
https://github.com/herval/zeppelin/tree/encrypt-credentials
If that's the kind of thing that may interest everyone else, I can get a PR
going
h
On Mon, Sep 25, 2017 at 7:07 AM, Adam Iezzi wrote:
> Yes, encrypting and storing the cre
Yes, encrypting and storing the credentials would be ideal. Essentially,
I'm looking for some sort of secrets store which can be accessed via the
Zeppelin paragraphs.
Adam
On Sun, Sep 24, 2017 at 6:30 AM, moon soo Lee wrote:
> Hi,
>
> "Credential" menu provides closest feature I think.
>
> Thro
Hi,
"Credential" menu provides closest feature I think.
Through "Credential" menu, each user can pass user-specific credential
informations to Interpreters. And interpreter can retrieve those
informations and use it internally. Also interpreter exposes API to user,
so user can access those inform
