tpalfy opened a new pull request, #7191: URL: https://github.com/apache/nifi/pull/7191
<!-- 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. --> # Summary [NIFI-8650](https://issues.apache.org/jira/browse/NIFI-8650) Created new component: FlowAnalyisRule. Added new framework functionality: analyze flow. FlowAnalysisRules can be managed from the UI: hamburger-menu -> Controller Settings -> Flow Analysis Rules FlowAnalysisRules can be set up with an enforcement policy (on the SETTINGS tab) that can have one of 2 values: WARN - Creates warnings through logs and bulletins. Doesn't impact the flow otherwise. ENFORCE - Apart from the warnings, also invalidates components that violate the rule. Flow analysis is run by the framework: -For the whole flow (starting at the root process group), scheduled every 5 minutes (similar to validation) -For each component individually, during their validation -For a process group (can be root), when requested asynchronously through REST interface (not from UI as of yet) Flow analysis may produce rule violations as a result. These are stored in memory and are not persisted. They -Can be requested through REST interface (not from UI as of yet) -In case of rules with ENFORCE enforcement policy, invalidate the corresponding components Currently, FlowAnalysisRule implementations are directly provided either -a component (currently supported Processors and ControllerServices) as VersionedComponent instances. Concrete type should be determined by the rule. -a process group as a VersionedProcessGroup. Indirectly they can analyze other components accessible from the directly provided components. Added one FlowAnalyisRule implementation: DisallowComponentType. It can be configured with the (simple or fully qualified) name of a type. Produces a rule violation for each supported component (currently controller service and processor) instances of that type. # 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-00000` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-00000` ### 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 11 - [ ] JDK 17 ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
