MTA-6288 Centralized configuration in Visual Studio Code plugin

docs/topics/vscode/proc_vscode-analyzing-application-using-profiles.adoc

@@ -0,0 +1,47 @@
+:_mod-docs-content-type: PROCEDURE
+[id="analyzing-application-profiles_{context}"]
+= Running an application analysis by using a profile
+
+[role="_abstract"]
+To run a static code analysis of an application, you can use a profile that is created and managed by your architect in the {ProductFullName} Hub. The centralized configuration management standardizes the analysis configuration and custom rules across projects to produce a consistent result. This allows the architect to create and manage the necessary profiles, thereby simplifying the lifecycle of analysis configurations and rules. Migrators can run analyses either by using local profile configuration or by using profiles from the Hub.
+
+When you connect to the Hub from your Visual Studio Code instance, {ProductShortName} downloads the analysis profiles and custom rules present in the Hub to the `.konveyor/profiles` location in your hard disk. You can use the analysis profile that contains custom rules to perform analyses in your Visual Studio Code IDE environment. If you connect to the Hub, the profile configuration options in your IDE instance are disabled.
+
+
+:FeatureName: Analysis Profile
+[IMPORTANT]
+====
+[subs="attributes+"]
+{FeatureName} is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.
+
+For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
+====
+:!FeatureName:
+
+.Prerequisites
+
+* You opened a project written in one of the supported languages in your Visual Studio Code workspace. {ProductShortName} can analyze source code written in `Java`, `C#`, `.NET`, `Node.js`, and `Python`.
+* An architect has configured an analysis profile in the Hub.
+
+.Procedure
+
+. Click the {mta-dl-plugin} extension and click *Open Analysis Panel*.
+
+. In settings (image:settings-icon.png[]), click *Configure Hub Settings* .
+
+. Configure the following settings on the *Hub Configuration* page:
+.. Enable *Hub*.
+.. Enter the {ProductShortName} user interface URL in the *Hub URL* field.
+.. If you want to connect to your Hub without verifying the local SSL certificate in the host, enable *Skip SSL certificate verification*. 
+.. Log in to the Hub by enabling the *Enable authentication* switch.
+.. Enter the username and password credentials of the {ProductShortName} user interface.
+.. To use the Solution Server to suggest resolutions for the issues in the source code, enable *Solution Server* .
+.. To sync the profiles with the Hub, enable *Profile Sync*. {ProductShortName} periodically downloads the latest version of the profiles from the Hub. {ProductShortName} does not update the profiles and rules if you do not sync the profiles with the Hub.
+
+. Select a profile from the list on the *{ProductShortName} Analysis View* page.
+. Click *Run Analysis*.
+
+
+[role="_additional-resources"]
+.Additional resources
+* link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/8.0/html/configuring_and_using_red_hat_developer_lightspeed_for_mta/index[Configuring and using Developer Lightspeed for {ProductShortName}]

docs/vs-code-extension-guide/master.adoc

@@ -26,6 +26,8 @@ include::topics/vscode/proc_configuring-lighstspeed-ide-settings.adoc[leveloffse
 include::topics/vscode/proc_configuring-profile-settings.adoc[leveloffset=+1]
 
 include::topics/vscode/proc_vscode-analyzing-application.adoc[leveloffset=+1]
+
+include::topics/vscode/proc_vscode-analyzing-application-using-profiles.adoc[leveloffset=+1]
 
 include::topics/vscode/proc_vscode-reviewing-and-resolving-issues.adoc[leveloffset=+1]