[
https://issues.apache.org/jira/browse/NIFI-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15423775#comment-15423775
]
ASF GitHub Bot commented on NIFI-2574:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/872
As of right now, I have merged these commits into [PR
834](https://github.com/apache/nifi/pull/834/commits/d4ad014cf6ba0ded6a69f3532aacf41ce0260b89)
and the build compiles, checkstyle passes, and all current tests pass.
There is still substantial cleanup work to do and because of the change
from `NiFiProperties.getInstance()` to using `NiFiPropertiesLoader.get()`, the
integration with Spring for *web-api* still needs to occur.
Thanks for the help @joewitt .
> Update NiFiProperties usage to a context based accessor rather than static
> singleton
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Configuration, Core Framework
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Labels: migration
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of
> NiFiProperties which enables a loader to exist which will encapsulate all
> logic for dealing with encrypted properties as is the goal of the parent task.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
