[ https://issues.apache.org/jira/browse/NIFI-4801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16334583#comment-16334583 ]
Daniel Chaffelson commented on NIFI-4801: ----------------------------------------- [~mcgilman] Yeah this duplicates that issue, though perhaps with a little more detail and test code/documentation to look at. Up to you which to move forward. I would also suggest that you look at the way Export Template works to make sure it's producing a consistent experience perhaps? > Rest-api swagger definition produces non-functional template import in Python > ----------------------------------------------------------------------------- > > Key: NIFI-4801 > URL: https://issues.apache.org/jira/browse/NIFI-4801 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.5.0 > Environment: Python 2.7/3.6 > Reporter: Daniel Chaffelson > Assignee: Kevin Doran > Priority: Minor > > The swagger.json produced when compiling NiFi-1.5.0 results in a > ProcessgroupsApi().upload_template function that only accepts the id of the > Process Group to receive the template, and no option to specify the template > itself. > It would appear that the underlying API call expects the template to be the > body of the request, but the produced function does not allow it to be > specified. This is changed from NiFi-1.2.0 where a 'template' keyword > argument was included. > It may also be related to how the TemplatesApi().export_template function > used to produce a TemplateDTO and now produces a string. > I am unsure in which version since 1.2.0 this changed, it may not > specifically be just 1.5.0 code. > An example of the procedurally generated code can be found at: > [https://github.com/Chaffelson/nifi-python-swagger-client/blob/master/swagger_client/apis/processgroups_api.py] > And documentation at: > [http://nifi-python-swagger-client.readthedocs.io/en/latest/ProcessgroupsApi/#upload_template] -- This message was sent by Atlassian JIRA (v7.6.3#76005)