[jira] [Updated] (NIFI-2785) Template Upload - Unable to upload to descendant group

2016-09-21 Thread Bryan Bende (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bryan Bende updated NIFI-2785:
--
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Template Upload - Unable to upload to descendant group
> --
>
> Key: NIFI-2785
> URL: https://issues.apache.org/jira/browse/NIFI-2785
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
> Fix For: 1.1.0
>
>
> Templates can be uploaded to any Process Group. This is driven by the URL 
> used during the upload request. Currently, the URL in the UI for the upload 
> request is initialized with the root group id and never updated. As a result, 
> through the UI templates can only be uploaded to the root group.
>  
> As a work-around, templates could still be uploaded to descendant groups via 
> a request directly to the REST API. This can be done using the following 
> command:
> {noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
> http://{host}:{port}/nifi-api/process-groups/{process-group-id}/templates/upload{noformat}
> Additionally, templates uploaded to the root group could have explicit 
> policies set to share with other users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (NIFI-2785) Template Upload - Unable to upload to descendant group

2016-09-19 Thread Matt Gilman (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2785:
--
Status: Patch Available  (was: Open)

> Template Upload - Unable to upload to descendant group
> --
>
> Key: NIFI-2785
> URL: https://issues.apache.org/jira/browse/NIFI-2785
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Critical
> Fix For: 1.1.0
>
>
> Templates can be uploaded to any Process Group. This is driven by the URL 
> used during the upload request. Currently, the URL in the UI for the upload 
> request is initialized with the root group id and never updated. As a result, 
> through the UI templates can only be uploaded to the root group.
>  
> As a work-around, templates could still be uploaded to descendant groups via 
> a request directly to the REST API. This can be done using the following 
> command:
> {noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
> http://{host}:{port}/nifi-api/process-groups/{process-group-id}/templates/upload{noformat}
> Additionally, templates uploaded to the root group could have explicit 
> policies set to share with other users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (NIFI-2785) Template Upload - Unable to upload to descendant group

2016-09-16 Thread Matt Gilman (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2785:
--
Description: 
Templates can be uploaded to any Process Group. This is driven by the URL used 
during the upload request. Currently, the URL in the UI for the upload request 
is initialized with the root group id and never updated. As a result, through 
the UI templates can only be uploaded to the root group.
 
As a work-around, templates could still be uploaded to descendant groups via a 
request directly to the REST API. This can be done using the following command:

{noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
http://{host}:{port}/nifi-api/process-groups/{process-group-id}/templates/upload{noformat}

Additionally, templates uploaded to the root group could have explicit policies 
set to share with other users.

  was:
Templates can be uploaded to any Process Group. This is driven by the URL used 
during the upload request. Currently, the URL in the UI for the upload request 
is initialized with the root group id and never updated. As a result, through 
the UI templates can only be uploaded to the root group.
 
As a work-around, templates could still be uploaded to descendant groups via a 
request directly to the REST API. This can be done using the following command:

{noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
http://{host}:{port}nifi-api/process-groups/{process-group-id}/templates/upload{noformat}

Additionally, templates uploaded to the root group could have explicit policies 
set to share with other users.


> Template Upload - Unable to upload to descendant group
> --
>
> Key: NIFI-2785
> URL: https://issues.apache.org/jira/browse/NIFI-2785
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Priority: Critical
> Fix For: 1.1.0
>
>
> Templates can be uploaded to any Process Group. This is driven by the URL 
> used during the upload request. Currently, the URL in the UI for the upload 
> request is initialized with the root group id and never updated. As a result, 
> through the UI templates can only be uploaded to the root group.
>  
> As a work-around, templates could still be uploaded to descendant groups via 
> a request directly to the REST API. This can be done using the following 
> command:
> {noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
> http://{host}:{port}/nifi-api/process-groups/{process-group-id}/templates/upload{noformat}
> Additionally, templates uploaded to the root group could have explicit 
> policies set to share with other users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (NIFI-2785) Template Upload - Unable to upload to descendant group

2016-09-16 Thread Matt Gilman (JIRA)

 [ 
https://issues.apache.org/jira/browse/NIFI-2785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-2785:
--
Description: 
Templates can be uploaded to any Process Group. This is driven by the URL used 
during the upload request. Currently, the URL in the UI for the upload request 
is initialized with the root group id and never updated. As a result, through 
the UI templates can only be uploaded to the root group.
 
As a work-around, templates could still be uploaded to descendant groups via a 
request directly to the REST API. This can be done using the following command:

{noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
http://{host}:{port}nifi-api/process-groups/{process-group-id}/templates/upload{noformat}

Additionally, templates uploaded to the root group could have explicit policies 
set to share with other users.

  was:
Templates can be uploaded to any Process Group. This is driven by the URL used 
during the upload request. Currently, the URL in the UI for the upload request 
is initialized with the root group id and never updated. As a result, through 
the UI templates can only be uploaded to the root group.
 
As a work-around, templates could still be uploaded to descendant groups via a 
request directly to the REST API. Additionally, templates uploaded to the root 
group could have explicit policies set to share with other users.


> Template Upload - Unable to upload to descendant group
> --
>
> Key: NIFI-2785
> URL: https://issues.apache.org/jira/browse/NIFI-2785
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Priority: Critical
> Fix For: 1.1.0
>
>
> Templates can be uploaded to any Process Group. This is driven by the URL 
> used during the upload request. Currently, the URL in the UI for the upload 
> request is initialized with the root group id and never updated. As a result, 
> through the UI templates can only be uploaded to the root group.
>  
> As a work-around, templates could still be uploaded to descendant groups via 
> a request directly to the REST API. This can be done using the following 
> command:
> {noformat}curl -X POST -v -F template=@"/path/to/template.xml" 
> http://{host}:{port}nifi-api/process-groups/{process-group-id}/templates/upload{noformat}
> Additionally, templates uploaded to the root group could have explicit 
> policies set to share with other users.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)