[
https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065454#comment-15065454
]
Matt Gilman commented on NIFI-826:
----------------------------------
Sorry, forgot to address your question. Yes, SnippetUtils.populateSnippet is a
good place to start. Just an additional heads up the Snippet concept is used
when doing a Copy/Paste action as well as Template creation.
Also, SnippetUtils.copyContentsForGroup is where a snippet is currently
instantiated (imported into a specific Process Group). I point you here because
that is where the source/destination IDs in connections are currently handled.
This logic will now need to be performed when the template is generated instead
of when its imported into a specific group.
> Export templates in a deterministic way
> ---------------------------------------
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
>
> Templates should be exported in a deterministic way so that they can be
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some
> settings are ignored (run state).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
