Add @Secret annotation to mask data in steps#465
Conversation
|
|
a80bde2 to
964860e
Compare
|
@baev Is anyone looking at these PR's? I don't have access to assign them to anyone... |
|
@baev I see a "continuous-integration/jenkins/pr-merge — This commit cannot be built" message but when I click details it gives me a 404 error. What do I need to do to get this PR merged? |
|
closed via #648 |
|
@secret annotation is available in allure 2 version |
|
@Nagesh389 Apparently @baev didn't like the simple @secret annotation I proposed and went with this option instead: #648 |
|
@cpjust Thank you so much for the support and quick response. |
|
Could you please show me how to use it? |
|
Can someone share the example to use @secret ? |
|
please do not comment on closed PR. You can create a discussions instead if you have some questions or raise an issue for a bugs. BTW you can find all the information you need here #648 |
Context
Fixes: allure-framework/allure2#392 and allure-framework/allure2#863
This PR adds a new @secret annotation for step parameters which will prevent the value of sensitive information (such as passwords or credit cards) from being displayed in the Allure report and will instead print *****.
Checklist