docker/test/integration/features/s2s.feature

# Licensed to the Apache Software Foundation (ASF) under one or more
# contributor license agreements.  See the NOTICE file distributed with
# this work for additional information regarding copyright ownership.
# The ASF licenses this file to You under the Apache License, Version 2.0
# (the "License"); you may not use this file except in compliance with
# the License.  You may obtain a copy of the License at
#
#     http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.

@CORE
Feature: Sending data from MiNiFi-C++ to NiFi using S2S protocol
  In order to transfer data inbetween NiFi and MiNiFi flows
  As a user of MiNiFi
  I need to have RemoteProcessGroup flow nodes

  Background:
    Given the content of "/tmp/output" is monitored

  Scenario: A MiNiFi instance produces and transfers data to a NiFi instance via s2s
    Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And a file with the content "test" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "http://nifi-${feature_id}:8080/nifi"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup

    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "test" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds

  Scenario: A MiNiFi instance produces and transfers a large data file to a NiFi instance via s2s
    Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And a file with the content "this is a very long file we want to send by site-to-site" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "http://nifi-${feature_id}:8080/nifi"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup

    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "this is a very long file we want to send by site-to-site" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds

  Scenario: Zero length files are transfered between via s2s if the "drop empty" connection property is false
    Given a MiNiFi CPP server with yaml config
    And a GenerateFlowFile processor with the "File Size" property set to "0B"
    And a RemoteProcessGroup node opened on "http://nifi-${feature_id}:8080/nifi"
    And the "success" relationship of the GenerateFlowFile processor is connected to the input port on the RemoteProcessGroup

    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then at least one empty flowfile is placed in the monitored directory in less than 90 seconds

  Scenario: Zero length files are not transfered between via s2s if the "drop empty" connection property is true
    # "drop empty" is only supported with yaml config
    Given a MiNiFi CPP server with yaml config
    And a GenerateFlowFile processor with the "File Size" property set to "0B"
    And a RemoteProcessGroup node opened on "http://nifi-${feature_id}:8080/nifi"
    And the "success" relationship of the GenerateFlowFile processor is connected to the input port on the RemoteProcessGroup
    And the connection going to the RemoteProcessGroup has "drop empty" set

    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then no files are placed in the monitored directory in 50 seconds of running time

  Scenario: A MiNiFi instance produces and transfers data to a NiFi instance via s2s using SSL
    Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And the "Keep Source File" property of the GetFile processor is set to "true"
    And a file with the content "test" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "https://nifi-${feature_id}:8443/nifi"
    And a SSL context service is set up for the following remote process group: "RemoteProcessGroup"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup

    And SSL is enabled in NiFi flow
    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "test" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds

  Scenario: A MiNiFi instance produces and transfers data to a NiFi instance via s2s using SSL with YAML config
    Given a MiNiFi CPP server with yaml config
    And a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And the "Keep Source File" property of the GetFile processor is set to "true"
    And a file with the content "test" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "https://nifi-${feature_id}:8443/nifi"
    And a SSL context service is set up for the following remote process group: "RemoteProcessGroup"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup

    And SSL is enabled in NiFi flow
    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "test" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds

  Scenario: A MiNiFi instance produces and transfers data to a NiFi instance via s2s using SSL config defined in minifi.properties
    Given a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And the "Keep Source File" property of the GetFile processor is set to "true"
    And a file with the content "test" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "https://nifi-${feature_id}:8443/nifi"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup
    And SSL properties are set in MiNiFi

    And SSL is enabled in NiFi flow
    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "test" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds

  Scenario: A MiNiFi instance produces and transfers data to a NiFi instance via s2s using YAML config and SSL config defined in minifi.properties
    Given a MiNiFi CPP server with yaml config
    And a GetFile processor with the "Input Directory" property set to "/tmp/input"
    And the "Keep Source File" property of the GetFile processor is set to "true"
    And a file with the content "test" is present in "/tmp/input"
    And a RemoteProcessGroup node opened on "https://nifi-${feature_id}:8443/nifi"
    And the "success" relationship of the GetFile processor is connected to the input port on the RemoteProcessGroup
    And SSL properties are set in MiNiFi

    And SSL is enabled in NiFi flow
    And a NiFi flow receiving data from a RemoteProcessGroup "from-minifi"
    And a PutFile processor with the "Directory" property set to "/tmp/output" in the "nifi" flow
    And the "success" relationship of the from-minifi is connected to the PutFile

    When both instances start up
    Then a flowfile with the content "test" is placed in the monitored directory in less than 90 seconds
    And the Minifi logs do not contain the following message: "ProcessSession rollback" after 1 seconds