Re: [PR] NIFI-12166 Add repo usage to the monitoring endpoint [nifi]
timeabarna commented on code in PR #7836: URL: https://github.com/apache/nifi/pull/7836#discussion_r1347115429 ## nifi-nar-bundles/nifi-extension-utils/nifi-prometheus-utils/pom.xml: ## @@ -53,6 +53,11 @@ nifi-metrics 2.0.0-SNAPSHOT + +org.apache.nifi +nifi-framework-api +2.0.0-SNAPSHOT + Review Comment: Thanks @markap14 for your review. I've modified the code based on your recommendations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12166 Add repo usage to the monitoring endpoint [nifi]
timeabarna commented on PR #7836: URL: https://github.com/apache/nifi/pull/7836#issuecomment-1752337190 Thank @markap14 for your review. I've modified the code based on your recommendations. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12178) Add integration-tests and docker-tests GithHub Action Workflows
[
https://issues.apache.org/jira/browse/NIFI-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773068#comment-17773068
]
Otto Fowler commented on NIFI-12178:
I think this stuff is great. The only thing I will add for consideration is
that Apache's GitHub resources are not infinite, ( join the build list for the
repetitive discussions on these limits as some projects exhaust them for all
the others ) and we should be cognizant of that.
> Add integration-tests and docker-tests GithHub Action Workflows
> ---
>
> Key: NIFI-12178
> URL: https://issues.apache.org/jira/browse/NIFI-12178
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are a lot of {{integration-tests}} and {{docker}} builds in the NiFi
> repository that aren't being regularly executed and verified.
> GitHub Action Workflows should be added (similar to the existing
> {{system-tests}} Workflow) that regularly exercise these tests, allowing the
> community to better monitor the health of NiFi components.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12192) GitHub Action Workflows could better report Tests Results and Summaries
Chris Sampson created NIFI-12192:
Summary: GitHub Action Workflows could better report Tests Results
and Summaries
Key: NIFI-12192
URL: https://issues.apache.org/jira/browse/NIFI-12192
Project: Apache NiFi
Issue Type: Improvement
Reporter: Chris Sampson
Fix For: 2.latest
Several of the GitHub Action Workflows produce {{JUnit}} XML result output
files through {{surefire}} and {{failsafe}} plugins. These are currently
uploaded as raw logs/XML files for people to download from GitHub, but it
should be possible to upload these results as {{checks}} within GitHub instead,
which would be easier for people to consume and understand what tests are
failing in their PRs.
One possible action to use would be
[test-reporter|https://github.com/marketplace/actions/test-reporter], although
an attempt to use this in NIFI-12177 as part of the new {{integration-tests}}
Workflow failed because it seems we're unable to {{write}} to the GitHub repo
(even with {code:yaml}permissions.checks: write{code} set within the Workflow
definition). This might be an intentional setting, and could require discussion
with the ASF Infrastructure team to understand whether this is/could be
permitted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12189) Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773023#comment-17773023 ] ASF subversion and git services commented on NIFI-12189: Commit a584251f0aba49dfad90fb0d36ab568effa7005d in nifi's branch refs/heads/main from Joe Gresock [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a584251f0a ] NIFI-12189: Upgrading PutCloudwatchMetric to use AWS SDK 2.x This closes #7857 Signed-off-by: Chris Sampson > Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries > -- > > Key: NIFI-12189 > URL: https://issues.apache.org/jira/browse/NIFI-12189 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12189) Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries
[ https://issues.apache.org/jira/browse/NIFI-12189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Sampson resolved NIFI-12189. -- Fix Version/s: 2.0.0 (was: 2.latest) Resolution: Fixed > Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries > -- > > Key: NIFI-12189 > URL: https://issues.apache.org/jira/browse/NIFI-12189 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Joe Gresock >Assignee: Joe Gresock >Priority: Minor > Fix For: 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12189: Upgrading PutCloudwatchMetric to use AWS SDK 2.x [nifi]
asfgit closed pull request #7857: NIFI-12189: Upgrading PutCloudwatchMetric to use AWS SDK 2.x URL: https://github.com/apache/nifi/pull/7857 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12190) Fix failing Integration Tests
[
https://issues.apache.org/jira/browse/NIFI-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17773022#comment-17773022
]
Chris Sampson commented on NIFI-12190:
--
NIFI-12144 will hopefully address a lot of the AWS-related ITs (although the
list in the {{integration-tests}}Â Workflow will need updating if [~markap14]'s
PR gets merged before NIFI-12178)
> Fix failing Integration Tests
> -
>
> Key: NIFI-12190
> URL: https://issues.apache.org/jira/browse/NIFI-12190
> Project: Apache NiFi
> Issue Type: Epic
>Reporter: Chris Sampson
>Priority: Major
> Fix For: 2.latest
>
>
> NIFI-12177 adds an {{integraiton-tests}} GitHub Actions Workflow to regularly
> run the {{integration-tests}} defined throughout the NiFi repo. However, many
> tests have had to be skipped from the {{failsafe plugin}} execution due to
> failures within the GitHub runner.
> Typically these are caused by:
> * the need for external resources to be setup
> * incorrect assertions that might have worked during the original IT creation
> but have not been updated since
> * or missing/incompatible OS resources within the GitHub runner
> This Epic is to review the failing ITs within NiFi codebase and either:
> * fix them, e.g. correct assertions, and/or by using Testcontainers for
> hosting external resources, such as for the Elasticsearch Processors
> * remove them if no longer useful/cannot be reliably executed on
> developer's/GitHub runners
> * annotate them to be skipped in CI environments if the tests are useful and
> work on a developer machine but won't be able to work in a CI runner, e.g. a
> [DisabledIfEnvironmentVariable|https://junit.org/junit5/docs/5.7.0/api/org.junit.jupiter.api/org/junit/jupiter/api/condition/DisabledIfEnvironmentVariable.html]
> to check whether the `CI` env var is present and set to `true`
> Once fixed, the appropriate entry from the {{integration-tests}} Workflow's
> {{MAVEN_FAILSAFE_SKIP_ITS}} env var **must** be removed
> At the time of writing, the ITs known to be failing (either in part or as a
> whole) are:
> {quote}!AwsSecretsManagerSensitivePropertyProviderIT,
> !AwsKmsSensitivePropertyProviderIT,
> !AzureKeyVaultKeySensitivePropertyProviderIT,
> !GcpKmsSensitivePropertyProviderIT,
> !StandardHashiCorpVaultCommunicationServiceIT,
> !ConversionWithSchemaInferenceIT#testXmlToAvro,
> !ConversionWithSchemaInferenceIT#testXmlToJson,
> !ConversionWithSchemaInferenceIT#testJsonToCsv,
> !ConversionWithSchemaInferenceIT#testCsvToXml,
> !ConversionWithSchemaInferenceIT#testXmlToAvroToXml,
> !ConversionWithSchemaInferenceIT#testCsvToAvro,
> !ConversionWithSchemaInferenceIT#testCsvToJson,
> !ConversionWithSchemaInferenceIT#testJsonToAvroToJson,
> !ConversionWithSchemaInferenceIT#testCsvToAvroToCsv,
> !ConversionWithExplicitSchemaIT#testJsonToCsv,
> !ConversionWithExplicitSchemaIT#testJsonToAvro,
> !ConversionWithExplicitSchemaIT#testJsonToAvroToJson,
> !ITConsumeKinesisStreamEndpointOverride,
> !ITConsumeKinesisStreamConnectAWS,
> !ITPutKinesisStream,
> !ITPutKinesisStreamWithEndpointOverride#testIntegrationSuccess,
> !ITPutKinesisFirehoseWithEndpointOverride#testIntegrationSuccess,
> !ITPutKinesisFirehose,
> !ITTagS3Object,
> !ITFetchS3Object,
> !ITDeleteS3Object,
> !ITPutS3Object,
> !ITListS3,
> !ITPutSNS#testPublish,
> !ITPutSNS#testPublishWithCredentialsProviderService,
> !ITDeleteSQS,
> !ITGetSQS,
> !ITPutSQS,
> !ITPutLambda,
> !GetMongoIT#testDatabaseEL,
> !PutGridFSIT#testFileNameAndHashUniqueness,
> !PutGridFSIT#testHashUniqueness,
> !ITPutAzureCosmosDBRecord,
> !ITListAzureBlobStorage_v12,
> !ITPutAzureDataLakeStorage,
> !ITFetchAzureDataLakeStorage,
> !ITListAzureDataLakeStorage,
> !ITFetchAzureBlobStorage_v12,
> !ITPutAzureBlobStorage_v12,
> !ITDeleteAzureDataLakeStorage,
> !ITDeleteAzureBlobStorage_v12,
> !ITMoveAzureDataLakeStorage,
> !AzureGraphUserGroupProviderIT,
> !JMSPublisherConsumerIT#validateMessageRedeliveryWhenNotAcked,
> !ITPutInfluxDB,
> !ITExecuteInfluxDBQuery,
> !GremlinClientServiceYamlSettingsAndBytecodeIT,
> !GremlinClientServiceControllerSettingsIT,
> !ITestConsumeEmail#validateUrl,
> !PrometheusReportingTaskIT#testNullLabel,
> !SnowflakeConnectionPoolIT,
> !SalesforceRestServiceIT,
> !QuerySalesforceObjectIT,
> !PutSalesforceObjectIT,
> !FetchDropboxIT,
> !PutDropboxIT,
> !ListDropboxIT,
> !FetchBoxFileIT,
> !PutBoxFileIT,
> !ListBoxFileIT,
> !JsonConfigBasedBoxClientServiceIT,
> !QueryIoTDBIT,
> !PutIoTDBRecordIT,
> !StandardProcessSessionIT#testCloneThenWriteCountsClaimReferencesProperly,
>
[jira] [Updated] (NIFI-12178) Add integration-tests and docker-tests GithHub Action Workflows
[
https://issues.apache.org/jira/browse/NIFI-12178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Sampson updated NIFI-12178:
-
Status: Patch Available (was: In Progress)
> Add integration-tests and docker-tests GithHub Action Workflows
> ---
>
> Key: NIFI-12178
> URL: https://issues.apache.org/jira/browse/NIFI-12178
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Chris Sampson
>Assignee: Chris Sampson
>Priority: Major
> Fix For: 2.latest
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> There are a lot of {{integration-tests}} and {{docker}} builds in the NiFi
> repository that aren't being regularly executed and verified.
> GitHub Action Workflows should be added (similar to the existing
> {{system-tests}} Workflow) that regularly exercise these tests, allowing the
> community to better monitor the health of NiFi components.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12178 add integration-tests and docker-tests github actions [nifi]
ChrisSamo632 opened a new pull request, #7858: URL: https://github.com/apache/nifi/pull/7858 # Summary [NIFI-12178](https://issues.apache.org/jira/browse/NIFI-12178) add integration-tests and docker-tests github actions # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - ~[ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html)` - ~[ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files~ ### Documentation - ~[ ] Documentation formatting appears as expected in rendered files~ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12190) Fix failing Integration Tests
[
https://issues.apache.org/jira/browse/NIFI-12190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Sampson updated NIFI-12190:
-
Description:
NIFI-12177 adds an {{integraiton-tests}} GitHub Actions Workflow to regularly
run the {{integration-tests}} defined throughout the NiFi repo. However, many
tests have had to be skipped from the {{failsafe plugin}} execution due to
failures within the GitHub runner.
Typically these are caused by:
* the need for external resources to be setup
* incorrect assertions that might have worked during the original IT creation
but have not been updated since
* or missing/incompatible OS resources within the GitHub runner
This Epic is to review the failing ITs within NiFi codebase and either:
* fix them, e.g. correct assertions, and/or by using Testcontainers for hosting
external resources, such as for the Elasticsearch Processors
* remove them if no longer useful/cannot be reliably executed on
developer's/GitHub runners
* annotate them to be skipped in CI environments if the tests are useful and
work on a developer machine but won't be able to work in a CI runner, e.g. a
[DisabledIfEnvironmentVariable|https://junit.org/junit5/docs/5.7.0/api/org.junit.jupiter.api/org/junit/jupiter/api/condition/DisabledIfEnvironmentVariable.html]
to check whether the `CI` env var is present and set to `true`
Once fixed, the appropriate entry from the {{integration-tests}} Workflow's
{{MAVEN_FAILSAFE_SKIP_ITS}} env var **must** be removed
At the time of writing, the ITs known to be failing (either in part or as a
whole) are:
{quote}!AwsSecretsManagerSensitivePropertyProviderIT,
!AwsKmsSensitivePropertyProviderIT,
!AzureKeyVaultKeySensitivePropertyProviderIT,
!GcpKmsSensitivePropertyProviderIT,
!StandardHashiCorpVaultCommunicationServiceIT,
!ConversionWithSchemaInferenceIT#testXmlToAvro,
!ConversionWithSchemaInferenceIT#testXmlToJson,
!ConversionWithSchemaInferenceIT#testJsonToCsv,
!ConversionWithSchemaInferenceIT#testCsvToXml,
!ConversionWithSchemaInferenceIT#testXmlToAvroToXml,
!ConversionWithSchemaInferenceIT#testCsvToAvro,
!ConversionWithSchemaInferenceIT#testCsvToJson,
!ConversionWithSchemaInferenceIT#testJsonToAvroToJson,
!ConversionWithSchemaInferenceIT#testCsvToAvroToCsv,
!ConversionWithExplicitSchemaIT#testJsonToCsv,
!ConversionWithExplicitSchemaIT#testJsonToAvro,
!ConversionWithExplicitSchemaIT#testJsonToAvroToJson,
!ITConsumeKinesisStreamEndpointOverride,
!ITConsumeKinesisStreamConnectAWS,
!ITPutKinesisStream,
!ITPutKinesisStreamWithEndpointOverride#testIntegrationSuccess,
!ITPutKinesisFirehoseWithEndpointOverride#testIntegrationSuccess,
!ITPutKinesisFirehose,
!ITTagS3Object,
!ITFetchS3Object,
!ITDeleteS3Object,
!ITPutS3Object,
!ITListS3,
!ITPutSNS#testPublish,
!ITPutSNS#testPublishWithCredentialsProviderService,
!ITDeleteSQS,
!ITGetSQS,
!ITPutSQS,
!ITPutLambda,
!GetMongoIT#testDatabaseEL,
!PutGridFSIT#testFileNameAndHashUniqueness,
!PutGridFSIT#testHashUniqueness,
!ITPutAzureCosmosDBRecord,
!ITListAzureBlobStorage_v12,
!ITPutAzureDataLakeStorage,
!ITFetchAzureDataLakeStorage,
!ITListAzureDataLakeStorage,
!ITFetchAzureBlobStorage_v12,
!ITPutAzureBlobStorage_v12,
!ITDeleteAzureDataLakeStorage,
!ITDeleteAzureBlobStorage_v12,
!ITMoveAzureDataLakeStorage,
!AzureGraphUserGroupProviderIT,
!JMSPublisherConsumerIT#validateMessageRedeliveryWhenNotAcked,
!ITPutInfluxDB,
!ITExecuteInfluxDBQuery,
!GremlinClientServiceYamlSettingsAndBytecodeIT,
!GremlinClientServiceControllerSettingsIT,
!ITestConsumeEmail#validateUrl,
!PrometheusReportingTaskIT#testNullLabel,
!SnowflakeConnectionPoolIT,
!SalesforceRestServiceIT,
!QuerySalesforceObjectIT,
!PutSalesforceObjectIT,
!FetchDropboxIT,
!PutDropboxIT,
!ListDropboxIT,
!FetchBoxFileIT,
!PutBoxFileIT,
!ListBoxFileIT,
!JsonConfigBasedBoxClientServiceIT,
!QueryIoTDBIT,
!PutIoTDBRecordIT,
!StandardProcessSessionIT#testCloneThenWriteCountsClaimReferencesProperly,
!StandardProcessSessionIT#testUpdateFlowFileRepoFailsOnSessionCommit,
!JMSPublisherConsumerIT#testMultipleThreads,
!ITRedisDistributedMapCacheClientService#testSentinelRedisWithAuthentication,
!ITRedisDistributedMapCacheClientService#testSentinelRedis,
!SnowflakePipeIT,
!SecureFileIT,
!SecureProxyIT#testAccessStatus,
!SecureProxyIT#testAccessStatusAsProxiedAdmin,
!SecureProxyIT#testAccessStatusUsingRegistryClient,
!SecureNiFiRegistryClientIT#testGetAccessStatus,
!SecureNiFiRegistryClientIT#testTenantsClientGroups,
!SecureNiFiRegistryClientIT#testTenantsClientUsers,
!SecureNiFiRegistryClientIT#testCrudOperations,
!SecureDatabaseIT
!ITConnectionAccessControl,
!ITLabelAccessControl,
[jira] [Created] (NIFI-12191) MacOS GitHub Runner does not correctly run Docker (Colima)
Chris Sampson created NIFI-12191:
Summary: MacOS GitHub Runner does not correctly run Docker (Colima)
Key: NIFI-12191
URL: https://issues.apache.org/jira/browse/NIFI-12191
Project: Apache NiFi
Issue Type: Bug
Reporter: Chris Sampson
Fix For: 2.latest
NIFI-12177 introduced the {{integration-tests}} and {{docker-tests}} GitHub
Action Workflows, which runs fine on {{Ubuntu}}, but cannot run as successfully
on {{MacOS}}.
This is because the MacOS runner **does not** contain Docker by default, and
installing it via {{brew install docker}} actually installs
[Colima|https://github.com/abiosoft/colima]. While this allows Docker Images to
be built and (to a degree) run as Containers, it has been noted that
Testcontainers **do not** work correctly with such a setup, and some of the
Docker Image Tests (e.g. for NiFi - see NIFI-12177) fail because containers
don't run in a consistent manner compared to Ubuntu with `docker` installed.
This ticket is to investigate and fix the use of Docker within the MacOS based
GitHub runner for these workflows.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12190) Fix failing Integration Tests
Chris Sampson created NIFI-12190:
Summary: Fix failing Integration Tests
Key: NIFI-12190
URL: https://issues.apache.org/jira/browse/NIFI-12190
Project: Apache NiFi
Issue Type: Epic
Reporter: Chris Sampson
Fix For: 2.latest
NIFI-12177 adds an {{integraiton-tests}} GitHub Actions Workflow to regularly
run the {{integration-tests}} defined throughout the NiFi repo. However, many
tests have had to be skipped from the {{failsafe plugin}} execution due to
failures within the GitHub runner.
Typically these are caused by:
* the need for external resources to be setup
* incorrect assertions that might have worked during the original IT creation
but have not been updated since
* or missing/incompatible OS resources within the GitHub runner
This Epic is to review the failing ITs within NiFi codebase and either:
* fix them, e.g. correct assertions, and/or by using Testcontainers for hosting
external resources, such as for the Elasticsearch Processors
* remove them if no longer useful/cannot be reliably executed on
developer's/GitHub runners
* annotate them to be skipped in CI environments if the tests are useful and
work on a developer machine but won't be able to work in a CI runner, e.g. a
[DisabledIfEnvironmentVariable|https://junit.org/junit5/docs/5.7.0/api/org.junit.jupiter.api/org/junit/jupiter/api/condition/DisabledIfEnvironmentVariable.html]
to check whether the `CI` env var is present and set to `true`
Once fixed, the appropriate entry from the {{integration-tests}} Workflow's
{{MAVEN_FAILSAFE_SKIP_ITS}} env var **must** be removed
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12189: Upgrading PutCloudwatchMetric to use AWS SDK 2.x [nifi]
gresockj opened a new pull request, #7857: URL: https://github.com/apache/nifi/pull/7857 # Summary [NIFI-12189](https://issues.apache.org/jira/browse/NIFI-12189) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12189) Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries
Joe Gresock created NIFI-12189: -- Summary: Upgrade AWS Cloudwatch Processors to use AWS 2.x libraries Key: NIFI-12189 URL: https://issues.apache.org/jira/browse/NIFI-12189 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Joe Gresock Assignee: Joe Gresock Fix For: 2.latest -- This message was sent by Atlassian Jira (v8.20.10#820010)
