[ 
https://issues.apache.org/jira/browse/HADOOP-15842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646366#comment-16646366
 ] 

Steve Loughran commented on HADOOP-15842:
-----------------------------------------

I should add I Don't know anything which actually uses this, but given its 
here, it should be kept current.

my little storediag util has an explicit list of properties for a store to 
fetch with a flag to indicate "sensitive", but doing a list of all store props 
and relying on regexps to filter is probably the better strategy, just to get 
that complete dump of all of the resolved config options of a store. So I might 
pick it up myself

> add fs.azure.account.oauth2.client.secret to 
> hadoop.security.sensitive-config-keys
> ----------------------------------------------------------------------------------
>
>                 Key: HADOOP-15842
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15842
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 3.2.0
>            Reporter: Steve Loughran
>            Assignee: Steve Loughran
>            Priority: Minor
>         Attachments: HADOOP-15842-001.patch
>
>
> in HADOOP-15839 I left out "fs.azure.account.oauth2.client.secret". Fix by 
> adding it



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org

Reply via email to