Conversation
how to find generated credentials in the logs adding default passwords security policy
|
Thanks for the pull request @laurentedel! As noted in the Pull Request checklist, each change requires an associated Jira issue number, so please open an issue in the Apache NiFi Jira board. You can also join the Developers mailing list and request Jira contributor access so that you can assign the issue to yourself. After opening the Jira issue, you can update this pull request to include the Jira number. |
|
This commit aims to resolve NIFI-9367 for Docker image usage details and clarification |
exceptionfactory
left a comment
There was a problem hiding this comment.
Thanks for creating a Jira issue and updating the pull request @laurentedel. Adding details to the Docker README is a helpful improvement, thanks for the contribution! I made several suggestions to align the wording with the project README.md, and also to correct spelling in a couple places.
Co-authored-by: exceptionfactory <exceptionfactory@apache.org>
Co-authored-by: exceptionfactory <exceptionfactory@apache.org>
Co-authored-by: exceptionfactory <exceptionfactory@apache.org>
Co-authored-by: exceptionfactory <exceptionfactory@apache.org>
|
Thank you for all your very valuable suggestions @exceptionfactory ! |
exceptionfactory
left a comment
There was a problem hiding this comment.
Thanks for making the changes @laurentedel, the latest updates look good! +1 Merging.
This closes apache#5511 Signed-off-by: David Handermann <exceptionfactory@apache.org>
how to find generated credentials in the logs
adding default passwords security policy
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
main)?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
squashor use--forcewhen pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean installat the rootnififolder?LICENSEfile, including the mainLICENSEfile undernifi-assembly?NOTICEfile, including the mainNOTICEfile found undernifi-assembly?.displayNamein addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.