[
https://issues.apache.org/jira/browse/NIFI-8557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Witt updated NIFI-8557:
---------------------------
Fix Version/s: (was: 1.14.0)
> Expose bootstrap properties in the ConfigTransformer
> ----------------------------------------------------
>
> Key: NIFI-8557
> URL: https://issues.apache.org/jira/browse/NIFI-8557
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Joe Percivall
> Assignee: Joe Percivall
> Priority: Major
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> The ConfigTransformer takes in the config.yml and creates the nifi.properties
> and flow.xml. In order to better support customizations on a per MiNiFi
> instance for things that aren't able to reference EL, we could expose the
> properties listed in the bootstrap.conf.
> As an example, the bootstrap conf could have properties identifying the S2S
> URL and port UUID to use. Then when MiNiFi pulls down the new config.yml it
> would translate the keys to their proper values as identified in the
> bootstrap.conf.
> The main unknown is what the "escape" identifiers would be. In EL it is "${
> ..... }" (not sure why Jira is formatting this with new lines). This would
> need to be specific enough that it doesn't collide with anything that'd be in
> the config.yml.
> Much further down the line, this could eventually evolve to expose ENV
> variables, key/values stored in a file, and maybe even basic functions as
> needed. Essentially a basic version of EL but I hesitate to call it that b/c
> I don't want users to expect all of that functionality. This should really be
> for things that can't be done via EL.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
