WIP - To be merged for 7.1 MTA-4016: Analyzer task RBAC

[anarnold97]

JIRA

• MTA-4016

There is some discussion about whether the warning should contain the example, e.g:

[WARNING]
.No multi-user access restrictions on resources
====
There are no multi-user access restrictions on resources.
An analyzer task created by a user, can be canceled by any other user.
====

Ilanit prefers without and Maayan prefers with. I am undecided

PREVIEW

• 3.5. Adding minimum requirements for Java analyzer and discovery
• 7.9.1. Configuring and running an application analysis

Snippet

Following Ilanit's comments, I have added the snippet to the top level of each book in the MTA docs:

• 1.1. About the CLI Guide
• 1.1. About the MTA plugin for Eclipse
• Getting started guide -Chapter 1. Introduction to the Migration Toolkit for Applications
• 1.1. About the MTA plugin for IntelliJ IDEA
• 1.1. About the Rule Development Guide
• 1.1. About the MTA extension for Microsoft Visual Studio Code
• 1.1. About the User Interface Guide
• Also added to RHSSO section:

[anarnold97]

@mguetta1 - please can you have a look, as i am not sure what else to add to the snippet, or where else this should be added?
Thanks

[istein1]

I suggest to remove the specific example of analyzer task access,
as we have the no multi-user access restriction on other resources as well.
Just leave the ".No multi-user access restrictions on resources" warning
and place it in the head of the MTA doc.

[mguetta1]

@anarnold97 thanks for this PR.
Could you please add this as a known issue rather than snippet?
And I am not sure about including this information in all the files here. From my point of view, I would like to see it as a known issue with the example that "An analyzer task created by a user, can be canceled by any other use" as a result

[anarnold97]

@anarnold97 thanks for this PR. Could you please add this as a known issue rather than snippet? And I am not sure about including this information in all the files here. From my point of view, I would like to see it as a known issue with the example that "An analyzer task created by a user, can be canceled by any other use" as a result

@mguetta1 - i will add as a Known Issue in another PR, so we are not relying on the readers looking at the release notes. See - MTA-4014: Custom rules in analysis Dependency rule is not fired

• 7.1.1 Known issues

• 7.1.0 Known issues