[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13206:
Resolution: Fixed
Status: Resolved (was: Patch Available)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13206:
Issue Type: Bug (was: Improvement)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-13206:
Priority: Minor (was: Major)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 2.0.0-M3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-13206) S3 Integration tests failing due to server-side encrypt enabled by default
[
https://issues.apache.org/jira/browse/NIFI-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Payne updated NIFI-13206:
--
Status: Patch Available (was: Open)
> S3 Integration tests failing due to server-side encrypt enabled by default
> --
>
> Key: NIFI-13206
> URL: https://issues.apache.org/jira/browse/NIFI-13206
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Mark Payne
>Assignee: Mark Payne
>Priority: Major
> Fix For: 2.0.0-M3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The 3.0 version of Localstack enabled S3 server-side encryption by default.
> This is causing integration tests now to fail with errors such as:
> {code:java}
> org.opentest4j.AssertionFailedError: Attribute s3.sseAlgorithm should not
> exist on FlowFile, but exists with value AES256 ==>
> Expected :false
> Actual :true {code}
> This is happening in both Fetch and Put S3 integration tests. They tests work
> as-is if we change the docker image of Localstack to 2.3.2
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
