Uploaded image for project: 'Apache NiFi'
  1. Apache NiFi
  2. NIFI-6825

Implement HashiCorp Vault Controller Service Configuration Properties

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Incomplete
    • None
    • None
    • None
    • None

    Description

      Hashicorp Vault controller service

      Dynamic property descriptors - key (component PD identifier) / value (Vault identifier/location)

      Components can reference controller service to populate property descriptors directly

      Scenarios:

      1. NiFi config values are stored in Vault & accessed via HVSPP

      2. NiFi flow details are stored in Vault & accessed via HVCS; config values are not

      3. Both are stored in Vault & accessed with HVSPP & HVCS

      1. Refactor common code out of the HVSPP to "VaultCommunicationService" (framework level)

      2. HVSPP delegates/wraps HVCommSvc (framework level)

      3. HVCS delegates/wraps HVCommSvc (extension level)

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tmelhase Troy Melhase
            tmelhase Troy Melhase
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0h
              0h
              Logged:
              Time Spent - 20m
              20m

              Slack

                Issue deployment