You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/01 19:10:00 UTC

[jira] [Commented] (NIFI-10071) Add Key/Value v2 support to StandardHashiCorpVaultCommunicationService

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

ASF subversion and git services commented on NIFI-10071:
--------------------------------------------------------

Commit 48de70a56883c69a7bc51545c7cd410563b995ec in nifi's branch refs/heads/main from Joe Gresock
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=48de70a568 ]

NIFI-10071: Adding support for HashiCorp Vault K/V version 2 Secrets Engine (#6087)



> Add Key/Value v2 support to StandardHashiCorpVaultCommunicationService
> ----------------------------------------------------------------------
>
>                 Key: NIFI-10071
>                 URL: https://issues.apache.org/jira/browse/NIFI-10071
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Joe Gresock
>            Assignee: Joe Gresock
>            Priority: Minor
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> The StandardHashiCorpVaultCommunicationService is currently hard-coded to use the Key/Value Version 1 secrets manager.  This could be more flexible by adding a property such as vault.kv.version=KV_2, which would default to KV_1 for backwards compatibility.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)