scottyaslan opened a new pull request #3606: [WIP] Nifi 6282 URL: https://github.com/apache/nifi/pull/3606 This PR introduces the management of parameters and parameter contexts. It is a WIP since it is dependent on https://github.com/apache/nifi/pull/3536 being merged first. -clear the parameter context name and description on “add parameter context dialog” (DONE) -hide the usage when updating a parameter context (DONE) -add combo to select parameter context from PG (DONE) - to unset a PG’s parameter context send a PG object with the parameterContextId as a null value (DONE) -add context menu to view parameter context for a PG (DONE) -verify context menu displays the parameters menu item only for a PG that has a parameter context set (DONE) -Editing non-sensitive parameter (DONE) -delete a parameter (DONE) - when editing a parameter context select the parameters tab by default (DONE) - create parameter context inline during PG configuration (DONE) - hide the info icon if no parameter description (DONE) - add access policies for parameters (DONE) - set permissions for parameter context (DONE) - update the description of a sensitive parameter(DONE) - only init parameter context tables once (DONE) - remove excessive api calls for parameter contexts (DONE) - update referencing components to use twisties and to scroll appropriately with appropriate borders (DONE) -parameter usages: verify Bulletins are being reported correctly for processor, CS, and unauthorized component (DONE) -need to try to set a sensitive parameter to a sensitive property (DONE) -need to try to set a sensitive parameter to a non-sensitive property (DONE) -parameter usages: verify the correct usages are being reported and verify the ability to GoTo affected processor, CS, or unauthorized component (DONE) -parameter usages: Need to get the process group and check the read privilege. If canRead is false then we should display the PG UUID (DONE) Thank you for submitting a contribution to Apache NiFi. Please provide a short description of the PR here: #### Description of PR _Enables X functionality; fixes bug NIFI-YYYY._ In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] 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. - [ ] Has your PR been rebased against the latest commit within the target branch (typically `master`)? - [ ] Is your initial contribution a single, squashed commit? _Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not `squash` or use `--force` when pushing to allow for clean monitoring of changes._ ### For code changes: - [ ] 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? - [ ] 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.
---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
