[
https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709840#comment-16709840
]
ASF GitHub Bot commented on NIFI-4621:
--------------------------------------
GitHub user kislayom opened a pull request:
https://github.com/apache/nifi/pull/3201
NIFI-4621
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [] Have you written or updated unit tests to verify your changes?
- [x] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/kislayom/nifi NIFI-4621
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/3201.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3201
----
commit 0512754739cf63785aebfc53a89bb75d37bacbed
Author: Kislay Kumar <kislay.osho@...>
Date: 2018-12-04T12:03:56Z
NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from
other processors, also validated the explression language is working for
properties of both the processors.
commit 9da3a8700244b4fdc06c634805bbc0b25369623a
Author: Kislay Kumar <kislay.osho@...>
Date: 2018-12-04T13:05:34Z
NIFI-4621 changes in processor ListSFTP and ListFTP to also have input
connection and expression language for properties
commit 4319d472a25fecc2bbb66501c98d91828470d15d
Author: Kislay Kumar <kislay.osho@...>
Date: 2018-12-04T12:03:56Z
NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from
other processors, also validated the explression language is working for
properties of both the processors.
NIFI-4621 changes in processor ListSFTP and ListFTP to also have input
connection and expression language for properties
commit d4321cf72085786f1f0b9453270fc6c7c5d32fe3
Author: kislayom <kislay.osho@...>
Date: 2018-12-05T09:25:26Z
Merge branch 'NIFI-4621' of https://github.com/kislayom/nifi into NIFI-4621
----
> Allow inputs to ListSFTP and ListFTP
> ------------------------------------
>
> Key: NIFI-4621
> URL: https://issues.apache.org/jira/browse/NIFI-4621
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.4.0
> Reporter: Soumya Shanta Ghosh
> Assignee: Kislay Kumar
> Priority: Critical
> Fix For: 1.9.0
>
>
> ListSFTP supports listing of the supplied directory (Remote Path)
> out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password"
> / "Private Key Passphrase".
> The password can change at a regular interval (depending on organization
> policy) or the Hostname or the Remote Path can change based on some other
> requirement.
> This is a case to allow ListSFTP to leverage the use of Nifi Expression
> language so that the values of Hostname, Password and/or Remote Path can be
> set based on the attributes of an incoming flow file.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)