[
https://issues.apache.org/jira/browse/NIFI-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15141634#comment-15141634
]
Joseph Witt commented on NIFI-1461:
-----------------------------------
I think it is fair game as-is. When one activates the RPM profile they are
following that profiles properties. The convenience binary we publish is the
tar.gz/zip and our release procedure does this without -Prpm. It is fine for a
specific call to -Prpm to happen in the specific case where the RPM is needed.
That is a great catch though.
We might need to slide this into 0.6.0 though as it is time for an RC/vote and
I want to make sure we have had sufficient discussion with Andre's concerns.
> RPM should create nifi user and give it access to the /opt/nifi and
> subdirectories
> ----------------------------------------------------------------------------------
>
> Key: NIFI-1461
> URL: https://issues.apache.org/jira/browse/NIFI-1461
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.4.1
> Reporter: Andre
> Assignee: Tony Kurc
> Labels: rpm
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1461-This-closes-204.-Implemented-RPM-before-af.patch,
> 0002-NIFI-1461-added-run.as-filtered-property-for-RPM-and.patch, nifi.spec,
> nifi.spec
>
>
> currently when installing from RPM the resulting permissions result on admins
> having to complete the installation by adding a user and correcting
> filesystem permissions.
> Ideally the RPM packages should result in installed files ready to be
> utilised as a non-root user
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
