fix: update microservices quickstart and ci pipeline

src/components/CollapsibleCode.js

@@ -0,0 +1,60 @@
+import React, {useState} from "react";
+import CodeBlock from "@theme/CodeBlock";
+
+export default function CollapsibleCode({
+  code,
+  language = "json",
+  previewLines = 10,
+}) {
+  const [expanded, setExpanded] = useState(false);
+  const codeLines = code.trim().split("\n");
+  const visibleCode = expanded
+    ? code.trim()
+    : codeLines.slice(0, previewLines).join("\n") + "\n# ...";
+
+  const handleCopy = () => {
+    try {
+      navigator.clipboard.writeText(code.trim());
+      const btn = document.getElementById("copy-full-code");
+      if (btn) {
+        const originalText = btn.innerText;
+        btn.innerText = "Copied!";
+        setTimeout(() => (btn.innerText = originalText), 2000);
+      }
+    } catch (err) {
+      console.error("Failed to copy code:", err);
+    }
+  };
+
+  return (
+    <div className="margin-vert--md">
+      {/* Pass the full code to CodeBlock so default copy button works */}
+      <CodeBlock language={language}>{visibleCode}</CodeBlock>
+
+      <div
+        style={{
+          display: "flex",
+          gap: "10px",
+          justifyContent: "flex-end",
+          marginTop: "-8px", // Pulls buttons closer to code block
+        }}
+      >
+        {codeLines.length > previewLines && (
+          <button
+            onClick={() => setExpanded(!expanded)}
+            className="button button--sm button--secondary"
+          >
+            {expanded ? "Show Less" : "Show More"}
+          </button>
+        )}
+        <button
+          id="copy-full-code"
+          onClick={handleCopy}
+          className="button button--sm button--primary"
+        >
+          Copy
+        </button>
+      </div>
+    </div>
+  );
+}

versioned_docs/version-3.0.0/ci-cd/github.md

@@ -21,7 +21,7 @@
 
 ## Shell Scripts
 
 GitHub scripts are the easiest way to integrate Keploy with GitHub. We will be using [express-mongoose](https://github.com/keploy/samples-typescript/tree/main/express-mongoose) sample-application for the example. You can either add the following script to yout `github workflow` or create a new worflow `.github/workflows/keploy-test.yml`:-
 
 ```yaml
 - name: Checkout Commit
@@ -34,10 +34,6 @@
   ...
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 ### Example with Scripts
 
 While using [express-mongoose](https://github.com/keploy/samples-typescript/tree/main/express-mongoose) sample-application with keploy test in GitHub CI, the workflow would like:-

versioned_docs/version-3.0.0/ci-cd/gitlab.md

@@ -41,10 +41,6 @@
     ...
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 Now that we have Keploy installed, and all ready, we need switch to path where `keploy` folder is present in our application and install all the application related dependencies. Since we are using [flask-mongo](https://github.com/keploy/samples-python) sample-application, steps in our `script:` would look like below:-
 
 ```yaml
@@ -66,17 +62,15 @@
 
 ### 📝 Note
 
-Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`...and thought, _"Wait, am I hacking the kernel or something?"_ 😅
+Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`
 
 Don’t worry — these are just there because **Keploy uses eBPF** (a cool Linux feature) to trace your app’s behavior.
 
 So we install `kmod`, `linux-headers-generic`, and `bpfcc-tools` to make that tracing possible.
 
-Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs` — it’s like giving Keploy the **backstage pass** it needs to watch your app in action.
-
-No black magic. Just some low-level Linux stuff helping your tests run like magic! 🪄✨
+Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs`
 
-We will get to see output : -
+We would output something like below:-
 
 ```sh
 $ keploy test -c "python3 app.py"  --delay 50
@@ -145,6 +139,6 @@
 
 ### 📦 Need the Full Pipeline?
 
 If you’re thinking, “This pipeline looks cool, but I need the _whole thing_ to integrate with your application!” — well, you're in luck! Check it out [here](https://github.com/keploy/samples-python) and get ready to copy-paste your way to success! ✨🚀
 
 Hope this helps you out, if you still have any questions, reach out to us .

versioned_docs/version-3.0.0/ci-cd/jenkins.md

@@ -19,9 +19,9 @@
 ## Prerequisites
 
 - Jenkins installed and running
 - Sudo access with `"NOPASSWORD"` via `jenkins ALL=(ALL) NOPASSWD: ALL`.
 
 Open terminal and run`sudo visudo` command to open the sudoers file and add the below line at the end of the file.
 
 ```sh
 jenkins ALL=(ALL) NOPASSWD: ALL
@@ -47,10 +47,6 @@
 
 ```
 
-> **Note: if you are using `arm_64` as runner use below to download keploy binary**
-
-`curl --silent --location "https://github.com/keploy/keploy/releases/latest/download/keploy_linux_arm64.tar.gz" | tar xz --overwrite -C /tmp`
-
 ### Example
 
 Now that we have Keploy installed, and all ready, we need switch to path where `keploy` folder is present in our application and install all the application related dependencies. Since we are using [gin-mongo](https://github.com/keploy/samples-go/tree/main/gin-mongo) sample-application, steps in our `script` would look like below:-
@@ -106,15 +102,13 @@
 
 ### 📝 Note
 
-Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`...and thought, _"Wait, am I hacking the kernel or something?"_ 😅
+Did you notice some weird stuff in the pipeline? Like `kmod`, `linux-headers`, `/sys/kernel/debug`
 
 Don’t worry — these are just there because **Keploy uses eBPF** (a cool Linux feature) to trace your app’s behavior.
 
 So we install `kmod`, `linux-headers-generic`, and `bpfcc-tools` to make that tracing possible.
 
-Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs` — it’s like giving Keploy the **backstage pass** it needs to watch your app in action.
-
-No black magic. Just some low-level Linux stuff helping your tests run like magic! 🪄✨
+Some CI systems don’t have `/sys/kernel/debug` and `/sys/kernel/tracing` by default, so we create them and mount `debugfs` and `tracefs`
 
 We would output something like below:-
 

versioned_docs/version-3.0.0/keploy-cloud/deduplication.md

@@ -1,7 +1,7 @@
 ---
 id: deduplication
-title: Remove Duplicates Tests 🧹
-sidebar_label: Remove Duplicate Tests 🧹
+title: Remove Duplicates Tests
+sidebar_label: Remove Duplicate Tests
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/installation.md

@@ -1,7 +1,7 @@
 ---
 id: cloud-installation
 title: Keploy Cloud Installation
-sidebar_label: Installation 🛠️
+sidebar_label: Installation
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/keploy-console.md

@@ -1,7 +1,7 @@
 ---
 id: keploy-console
-title: Keploy Console 📘
-sidebar_label: Keploy Console 🛠️
+title: Keploy Console
+sidebar_label: Keploy Console
 tags:
   - explanation
   - feature guide
@@ -68,7 +68,7 @@
 
 <img src="/docs/img/keploy-cloud/noise.png?raw=true" alt="Noise"/>
 
 You'd see the changes in the test-case file locally, new noisy fields are added under noise param in the test case.
 
 <img src="/docs/img/keploy-cloud/denoise.png?raw=true" alt="De-noise"/>
 

versioned_docs/version-3.0.0/keploy-cloud/mock-registry.md

@@ -1,7 +1,7 @@
 ---
 id: mock-registry
 title: Mock Registry
-sidebar_label: Mock Registry 📦
+sidebar_label: Mock Registry
 tags:
   - explanation
   - feature guide
@@ -15,7 +15,7 @@
 
 Mock Registry uploads mock files to cloud storage, keeping the application's repository lightweight and manageable.
 
 When dealing with large mock files during tests, committing them to git repositories can be cumbersome. **Uploading such mocks to cloud storage** instead helps maintain a clean and performant repository, reducing complexity.
 
 ## Usage 🛠️
 

versioned_docs/version-3.0.0/keploy-cloud/new-application.md

@@ -3,7 +3,7 @@ id: application-settings
 title: Keploy Cloud Application Settings Guide
 description: Learn how to configure application settings in Keploy Cloud. Manage environments, toggle features, and optimize your testing setup with this step-by-step guide.
 
-sidebar_label: Add Application 📝
+sidebar_label: Add Application
 tags:
   - explanation
   - feature guide

versioned_docs/version-3.0.0/keploy-cloud/testgeneration.md

@@ -1,7 +1,7 @@
 ---
 id: auto-test-generation
-title: Auto Test Generation 🚀
-sidebar_label: Test Generation 🚀
+title: Auto Test Generation
+sidebar_label: Test Generation
 tags:
   - Auto Test Generation
   - OpenAPI
@@ -416,7 +416,7 @@
 
 ## Generate test-cases
 
 Now that we have our schema file, we need to create create jar file since we are using java sample-application :-
 
 ```sh
 mvn clean install -DskipTests

versioned_docs/version-3.0.0/keploy-cloud/time-freezing.md

@@ -1,7 +1,7 @@
 ---
 id: time-freezing
 title: Time Freezing
-sidebar_label: Time Freezing 🥶
+sidebar_label: Time Freezing
 tags:
   - explanation
   - feature guide
@@ -46,7 +46,7 @@
 uname -a
 ```
 
 2. Download the the appropriate time freeze agent for your architecture & set the `LD_PRELOAD` Environment Variable in your Dockerfile
 
 ### For Golang(Go) Applications -