Merge pull request #491 from james-ha-bruno/updates-v2-15

Updates v2 15

Author: rreyn-bruno

components/premium-badge.tsx

@@ -3,22 +3,31 @@ import Link from "next/link";
 import { Badge } from "./ui/badge";
 
 export interface PremiumBadgeProps
-  extends React.HTMLAttributes<HTMLDivElement> {}
+  extends React.HTMLAttributes<HTMLDivElement> {
+  noLink?: boolean;
+}
+
+function PremiumBadge({ className, noLink, ...props }: PremiumBadgeProps) {
+  const badge = (
+    <Badge className="mx-3 sm:mx-6 rounded-lg px-1 w-fit flex-row gap-x-1 my-0" variant="warning">
+        Premium
+        <Image
+            src="/bruno.png"
+            alt="Bruno Logo"
+            height={20}
+            width={20}
+            className="my-0 h-5 w-5 sm:h-5 sm:w-5 group-hover:animate-infinite group-hover:animate-wiggle"
+        />
+    </Badge>
+  );
+
+  if (noLink) {
+    return badge;
+  }
 
-function PremiumBadge({ className, ...props }: PremiumBadgeProps) {
   return (
     <Link href="https://www.usebruno.com/pricing" target="_blank" className="my-0">
-        <Badge className="mx-3 sm:mx-6 rounded-lg px-1 w-fit flex-row gap-x-1 my-0" variant="warning">
-            Premium
-            <Image
-                src="/bruno.png"
-                alt="Bruno Logo"
-                height={16}
-                width={16}
-                className="my-0 h-5 w-5 sm:h-5 sm:w-5"
-                style={{ margin: 0 }}
-            />
-        </Badge>
+        {badge}
     </Link>
   );
 }

content/git-integration/_meta.js

@@ -3,6 +3,7 @@ export default {
   "using-cli": "Collaboration via CLI",
   "using-gui": "Collaboration via GUI",
   "gitlab": "GitLab",
+  "azure-devops": "Azure DevOps",
   "bitbucket": "Bitbucket",
   "embed-bruno-collection": "Fetch in Bruno Button"
-} 
+}

content/git-integration/azure-devops.mdx

@@ -0,0 +1,74 @@
+# Collaboration via Azure DevOps
+
+Azure DevOps is a comprehensive suite of development tools provided by Microsoft that enables teams to plan, develop, test, and deliver software efficiently. It offers integrated services including Azure Repos for Git repositories, Azure Pipelines for CI/CD, Azure Boards for work tracking, and more—making it a complete DevOps platform for enterprise teams.
+
+Bruno's Git functionality allows you to work with Azure DevOps to manage, collaborate, and maintain your API development workflow.
+
+## Configure Azure DevOps
+
+You need to set up an SSH key with Azure DevOps. While you can also set up personal access tokens (HTTPS), this requires you to enter your token on every operation. SSH is a more convenient and secure way to work with Azure DevOps.
+
+### Create Repository on Azure DevOps
+
+To get started, you have to create a project/repository on Azure DevOps. Follow these steps:
+
+1. Log into your Azure DevOps account at [dev.azure.com](https://dev.azure.com) (create one if you don't have one)
+2. Click on **+ New project** or select an existing project
+3. If creating a new project, fill in the required fields (Project name, Description, Visibility)
+4. Click **Create**
+5. Navigate to **Repos** in the left sidebar
+6. If you need to create a new repository within the project, click **+ New repository**
+
+![azure-devops-clone-url](/screenshots/git-integration/bitbucket-gitlab/ado-new-repo.webp)
+
+Once you have a repository, click on the **Clone** button in the top-right corner and copy the SSH URL, which looks similar to:
+
+![azure-devops-clone-url](/screenshots/git-integration/bitbucket-gitlab/ado-clone-ssh.webp)
+
+
+```bash
+[email protected]:v3/<organization>/<project>/<repo-name>
+```
+
+### Configure SSH Key
+
+Follow these steps to configure an SSH key on your local system:
+
+#### 1. Generate SSH Key
+
+Open your terminal and execute:
+
+```bash
+ssh-keygen -t ed25519 -C "[email protected]" -f ~/.ssh/id_ed25519_azuredevops
+```
+
+#### 2. Add SSH Key to SSH Agent
+
+Add the SSH key to your SSH agent so it can be used for authentication:
+
+```bash
+ssh-add ~/.ssh/id_ed25519_azuredevops
+```
+
+#### 3. Add the SSH Key to Your Azure DevOps Account
+
+1. Go to **Azure DevOps** > **User Settings** (click your avatar in the top-right) > **SSH public keys**
+2. Click **+ New Key**
+3. Give your key a name (e.g., "Bruno Development")
+4. Paste your `id_ed25519_azuredevops.pub` content in the **Public Key Data** field
+5. Click **Add**
+
+![azure-devops-add-ssh-key](/screenshots/git-integration/bitbucket-gitlab/ado-add-ssh-key.webp)
+
+## Use Azure DevOps with Bruno
+
+1. Create a Collection inside Bruno (if you haven't already)
+2. Click on the **Git** icon (next to Safe Mode) and select **Initialize repo**
+3. Click on **main** and select **Remotes** from the dropdown
+4. Add **origin** as the name of the remote and paste your repository URL (copied previously)
+
+Now you can perform push, pull, and other Git operations directly from Bruno.
+ 
+![bruno-git-operations](/screenshots/git-integration/bitbucket-gitlab/bruno-git-operations.webp)
+
+For more detailed information about Git operations in Bruno, check out the [Collaboration via GUI documentation](/git-integration/using-gui/intro).

content/license-administrators/saml-sso/overview.mdx

@@ -192,7 +192,7 @@ In the Bruno License Portal's SSO Settings, you'll find two fields under "Role M
 ### License Activation Flow
 
 **For User Role Users:**
-- Users can activate their Bruno license using SSO
+- [Users can activate their Bruno license using SSO](/license-end-users/activate-license#activating-with-sso)
 - They receive a license key via email on first login
 - They can use this key to activate Bruno on their local machine
 - They do NOT have access to the License Portal

content/license-end-users/activate-license.mdx

@@ -1,27 +1,60 @@
 import { Callout } from "nextra/components";
+import PremiumBadge from "@/components/premium-badge";
 
 # Activating Your License
 
 <Callout type="warning">
 You must be on Bruno v.1.35.0 or higher to activate a license after December 1, 2024
 </Callout>
 
+## Activating with License Key
+
 If you've been provisioned a license, you should have received a license key via email. If you have not received a key and already checked your spam folder, please reach out to your license administrator.
 
 ### Step 1: Click on the Settings or Key icon in Bruno
 
-Both icons are located at the bottom left corner of the Bruno window. The Key icon will take you directly to the `License` section. If you choose to use the Settings icon, simply select `License` from the settings menu. 
+Both icons are located at the bottom left corner of the Bruno window. The Key icon will take you directly to the `License` section. If you choose to use the Settings icon, simply select `License` from the settings menu.
 
-### Step 2: Enter License Details 
+### Step 2: Enter License Details
 
 Enter your license key and associated email address
 
 ![login](/screenshots/license-management/activatelicense.webp)
 
 <Callout type="info">
-If your company uses a self-hosted licensing server, select `License Server` and enter the details provided to you by your License Administrator. 
+If your company uses a self-hosted licensing server, select `License Server` and enter the details provided to you by your License Administrator.
 </Callout>
 
-### Step 4: License Activated
+### Step 3: License Activated
 
 Once the license is activated, you will see a success message.
+
+## Activating with SSO <PremiumBadge noLink />
+
+<Callout type="info">
+SSO license activation is available for Ultimate Edition customers. Please see the [SAML SSO Overview](/license-administrators/saml-sso/overview) for more information.
+</Callout>
+
+### Step 1: Click on the Settings or Key icon in Bruno
+
+Both icons are located at the bottom left corner of the Bruno window. The Key icon will take you directly to the `License` section. If you choose to use the Settings icon, simply select `License` from the settings menu.
+
+### Step 2: Activate with SSO
+
+If your company has configured SSO for Bruno, select `SSO` and click `Activate License`.
+
+![login](/screenshots/license-management/activate-sso.webp)
+
+<Callout type="info">
+Your email needs to be part of the SSO configuration in order to activate your license, with the `User Role` mapped. See [Role Mapping](/license-administrators/saml-sso/overview#role-mapping) for details.
+</Callout>
+
+### Step 3: SSO Login
+
+You will be redirected to your corporate SSO login page. Enter your credentials to login. 
+
+A successful login message will be displayed.
+
+![login](/screenshots/license-management/activate-message-success.webp)
+
+Returning to Bruno, you will see the license as activated.

content/license-overview.mdx

@@ -6,7 +6,7 @@ For our open-source users, there is no concept of license management! Simply dow
 
 Our commercial plans have different license management aspects. If you have any questions about what plan is best suited for you, please see our [pricing page <strong><sup>↗</sup></strong>](https://www.usebruno.com/pricing) or [contact us <strong><sup>↗</sup></strong>](mailto:[email protected]) to discuss.
 
-## License Management <PremiumBadge />
+## License Management <PremiumBadge noLink />
 
 ### For License Administrators
 

content/secrets-management/secret-managers/hashicorp-vault/adding-a-secret-provider.mdx

@@ -20,7 +20,7 @@ To configure a **Vault server** secret provider, you can opt for either **Token*
 
 4. Enter `http://localhost:8200` if using a local server, or the URL of the hosted server (e.g., `https://vault.example.com`).
 
-5. Provide the necessary [Token <strong><sup>↗</sup></strong>](https://developer.hashicorp.com/vault/docs/commands/token), [AppRole <strong><sup>↗</sup></strong>](https://developer.hashicorp.com/vault/tutorials/auth-methods/approle) and [LDAP <strong><sup>↗</sup></strong>](https://developer.hashicorp.com/vault/docs/auth/ldap) credentials.
+5. Provide the necessary [Token <strong><sup>↗</sup></strong>](https://developer.hashicorp.com/vault/docs/commands/token) or [AppRole <strong><sup>↗</sup></strong>](https://developer.hashicorp.com/vault/tutorials/auth-methods/approle) credentials.
 
 6. Click on **Add** to save the secret provider.
 

content/secrets-management/secret-masking.mdx

@@ -1,3 +1,5 @@
+import { Callout } from "nextra/components";
+
 # Bruno Secret Masking in Reports
 
 ## Overview
@@ -42,6 +44,10 @@ Bruno masks all values of environment variables marked as secret in the UI:
 
 **Result:** Every instance where `db_pass` is referenced appears masked in the report.
 
+<Callout type="info">
+When running via the Bruno CLI, the same masking rules apply. Secret variables passed using the `--env-var` flag are also masked in reports.
+</Callout>
+
 ### 4. External Secrets
 
 Bruno masks secrets fetched from external providers:

content/variables/interpolation.mdx

@@ -11,7 +11,9 @@ Variable interpolation in Bruno allows you to use variables in your requests usi
 ```javascript
 // Setting a string variable
 bru.setVar("greeting", "Hello World");
+```
 
+```http
 // Using in request
 GET http://api.example.com/{{greeting}}
 // Interpolates to: http://api.example.com/Hello World
@@ -22,7 +24,9 @@ GET http://api.example.com/{{greeting}}
 ```javascript
 // Setting a number variable
 bru.setVar("userId", 123);
+```
 
+```http
 // Using in request
 GET http://api.example.com/users/{{userId}}
 // Interpolates to: http://api.example.com/users/123
@@ -186,7 +190,9 @@ bru.setVar("searchParams", {
   offset: 0,
   filter: "active"
 });
+```
 
+```http
 // In URL
 GET http://api.example.com/users?limit={{searchParams.limit}}&offset={{searchParams.offset}}&filter={{searchParams.filter}}
 ```