Update CLI FAQ to support Proxy components

en/docs/choreo-cli/using-personal-access-tokens.md

@@ -0,0 +1,98 @@
+# Personal Access Tokens Guide for Choreo CLI
+
+## Introduction
+Personal Access Tokens (PATs) allow you to authenticate without using your primary credentials, adding an extra layer of security and ease of management. 
+
+---
+
+## Table of Contents
+
+1. [What Are Personal Access Tokens?](#what-are-personal-access-tokens)
+2. [Setting Up Personal Access Tokens](#setting-up-personal-access-tokens)
+3. [Using Personal Access Tokens with Choreo CLI](#using-personal-access-tokens-with-cli-tool)
+4. [Managing and Revoking Tokens](#managing-and-revoking-tokens)
+5. [Best Practices for Token Management](#best-practices-for-token-management)
+
+---
+
+### 1. What Are Personal Access Tokens?
+Personal Access Tokens (PATs) are unique strings that allow you to authenticate without requiring a username and 
+password each time. PATs are associated with your account and can be created for specific use cases, allowing granular 
+access to your app resources.
+
+> **Note:** PATs should be treated like passwords and stored securely.
+
+---
+
+### 2. Setting Up Personal Access Tokens
+
+To use Personal Access Tokens with the Choreo CLI, follow these steps to set up and retrieve a token from 
+the Choreo Console.
+
+#### Step 1: Log into Your Account
+1. Go to [Choreo Console](https://console.choreo.dev).
+2. Navigate to **Account Settings**.
+3. From the Account settings page go to **Personal Access Tokens** section.
+
+![UserMenu](../assets/img/choreo-cli/personal-access-tokens/user-menu.png)
+![AccountSettings](../assets/img/choreo-cli/personal-access-tokens/account-settings.png)
+
+#### Step 2: Generate a New Token
+1. Click on **Create New**.
+2. Specify a name for your token and define its scope and permissions by default this would select all the necessary 
+scopes for the CLI to function.
+3. Click **Generate**.
+
+![GenerateForm](../assets/img/choreo-cli/personal-access-tokens/create-pat.png)
+![GenerateForm](../assets/img/choreo-cli/personal-access-tokens/generated-pat.png)
+
+4. Copy the token shown on the screen and store it securely. You won’t be able to view it again.
+
+> **Warning:** Treat your token as confidential information. Do not share it or store it in unsecured files.
+
+---
+
+### 3. Using Personal Access Tokens with Choreo CLI
+
+After generating your token, you can use it with Choreo CLI for various operations. Here’s how to authenticate with 
+a Personal Access Token.
+
+#### Command Syntax
+To use a token, use the login command with the flag `--with-token`:
+
+```bash
+choreo login --with-token
+```
+
+This command would read the token from the standard input
+
+**Example:**
+```bash
+export CHOREO_TOKEN=<YOUR_PERSONAL_ACCESS_TOKEN>
+echo "$CHOREO_TOKEN" | choreo login --with-token
+```
+
+> **Note:** Replace `YOUR_PERSONAL_ACCESS_TOKEN` with your actual token.
+
+---
+
+### 4. Managing and Revoking Tokens
+
+To manage or revoke existing tokens, return to the **Personal Access Tokens** section in your account settings.
+
+1. Locate the token you want to revoke.
+2. Click on **Revoke** next to the token.
+
+> **Tip:** Regularly review and revoke tokens that are no longer in use to maintain security.
+
+![PatListing](../assets/img/choreo-cli/personal-access-tokens/pat-listing.png)
+
+---
+
+### 5. Best Practices for Token Management
+
+- **Limit Scope:** Only grant the permissions needed for each use case.
+- **Rotate Tokens Regularly:** Replace tokens periodically to reduce the risk of compromise.
+- **Use Secure Storage:** Store tokens in a secure location, such as a secrets manager.
+- **Revoke Unused Tokens:** Regularly audit and revoke tokens no longer required.
+

en/docs/references/faq.md

@@ -613,6 +613,19 @@ The build configurations required for existing buildpacks are as follows:
             <ul> 
          </td>
       </tr>
+      <tr>
+        <td>API proxy</td>
+        <td>n/a</td>
+        <td>
+            <ul>
+               <li>version: Api version in the form vX.X</li>
+               <li>context: Context for the API url</li>
+               <li>schemaFilePath: Open API specification file path relative to the component directory</li>
+               <li>endpointUrl: Target Endpoint url for the proxy</li>
+               <li>accessibility: Mode of the access for the API(internal|external)</li>
+            </ul>
+        </td>
+      </tr>
    </tbody>
 </table>