Merge branch 'master' into release-4-5-c

Author: karl-cardenas-coding

.dockerignore

@@ -9,3 +9,6 @@ screenshots/
 tests/screenshot.spec.ts-snapshots/
 tests-results/
 playwright-report/
+.docusaurus/
+.git
+.github

.prettierignore

@@ -6,6 +6,7 @@ src/deprecated
 vale/
 **/*.yaml
 **/*.yml
+.dockerignore
 
 docs/api-content/**/*.json
 

Dockerfile

@@ -2,15 +2,21 @@ FROM node:20-alpine
 
 WORKDIR /librarium
 
-COPY ./scripts/entry.sh /entry.sh
+ENV DISABLE_PACKS_INTEGRATIONS=true
+ENV DISABLE_SECURITY_INTEGRATIONS=true
+
 COPY --chown=node . .
-RUN apk add util-linux && \
-chmod +x /entry.sh && \
-mkdir .cache && \
-npm ci && \
-chown -R node:node /librarium
+
+RUN apk add --no-cache util-linux bash && \
+    npm install @docusaurus/faster &&\
+    npm ci && \
+    chmod -R +x scripts 
+
+
+RUN chown -R node:node /librarium
+
 
 EXPOSE 9000
 USER node
-ENTRYPOINT ["/entry.sh"]
-CMD ["npm", "run", "start"]
+
+CMD ["npm","run","start"]

Makefile

@@ -85,11 +85,11 @@ init: ## Initialize npm dependencies
 	grep -q "^ALGOLIA_APP_ID=" .env || echo "\nALGOLIA_APP_ID=1234567890" >> .env
 	grep -q "^ALGOLIA_SEARCH_KEY=" .env || echo "\nALGOLIA_SEARCH_KEY=1234567890" >> .env
 	grep -q "^ALGOLIA_INDEX_NAME=" .env || echo "\nALGOLIA_INDEX_NAME=spectrocloud" >> .env
+	grep -q "^DSO_AUTH_TOKEN=" .env || echo "\nDISABLE_SECURITY_INTEGRATIONS=true\nDSO_AUTH_TOKEN=" >> .env
+	grep -q "^PALETTE_API_KEY=" .env || echo "\nDISABLE_PACKS_INTEGRATIONS=true" >> .env
 	npx husky install
 
 start: ## Start a local development server
-	make generate-partials
-	npm run cves
 	npm run start
 
 start-cached-packs: ## Start a local development server with cached packs retry.
@@ -183,8 +183,8 @@ commit: ## Add a Git commit. Usage: make commit MESSAGE="<your message here>"
 docker-image: ## Build the docker image
 	docker build -t $(IMAGE) .
 
-docker-start: docker-image ## Start a local development container
-	docker run --env-file=.env --rm -it -v $(CURDIR)/docs:/librarium/docs/ -p 9000:9000 $(IMAGE)
+docker-start: docker-image ## Build the docker image and start a local development container
+	docker run --env-file=.env --rm -it -v $(CURDIR)/docs:/librarium/docs/ -v $(CURDIR)/_partials/:/librarium/_partials/ -p 9000:9000 $(IMAGE)
 
 
 ##@ Writing Checks
@@ -296,4 +296,4 @@ update-dev-index: ## Update the Algolia index for the dev environment
 
 remove-dev-index: ## Remove the Algolia index for the dev environment
 	@echo "removing Algolia index for dev environment"
-	algolia index delete dev-docusaurus-librarium --confirm
+	algolia index delete dev-docusaurus-librarium --confirm

README.md

@@ -38,10 +38,13 @@ Initialize the repository by issuing the following command:
 make init
 ```
 
-Next, add your Palette API key to the `.env` file. Replace `<your-palette-api-key>` with your Palette API key.
+By default, the [Packs component](#packs-component) is disabled. If you would like to enable it, then add your Palette
+API key and set `DISABLE_PACKS_INTEGRATIONS` to `false` in the `.env` file. Replace `<your-palette-api-key>` with your
+Palette API key.
 
 ```shell
 PALETTE_API_KEY="<your-palette-api-key>"
+DISABLE_PACKS_INTEGRATIONS=false
 ```
 
 > [!IMPORTANT] You need a Palette API key to start the local development server. Refer to the

docs/api-content/api-docs/2-samples.md

@@ -69,13 +69,30 @@ want to deploy the cluster, such as public cloud or on-prem.
 
 **Endpoint**: `https://api.spectrocloud.com/v1/spectroclusters/{provider}`
 
-Set the provider as an environment variable.
+The following table outlines all available provider options.
+
+| **Provider**                                   | **Value**     |
+| ---------------------------------------------- | ------------- |
+| **Azure IaaS**                                 | `azure`       |
+| **Azure AKS**                                  | `aks`         |
+| **AWS IaaS**                                   | `aws`         |
+| **AWS EKS**                                    | `eks`         |
+| **GCP IaaS**                                   | `gcp`         |
+| **GCP GKE**                                    | `gke`         |
+| **TKE** (Tencent)                              | `tke`         |
+| **MAAS** (Canonical)                           | `maas`        |
+| **VMware vSphere**                             | `vsphere`     |
+| **Openstack**                                  | `openstack`   |
+| **Edge Native**                                | `edge-native` |
+| [**Virtual**](/devx/palette-virtual-clusters/) | `virtual`     |
+
+Set the provider as an environment variable. For example, issue the following command to set Azure IaaS as the provider.
 
 ```shell
-export PROVIDER="Your Provider"
+export PROVIDER="azure"
 ```
 
-<br />
+Example payload.
 
 ```shell
 export PAYLOAD='{
@@ -93,10 +110,10 @@ export PAYLOAD='{
 <TabItem label="curl" value="cluster-create-curl">
 
 ```shell
-curl --location 'https://api.spectrocloud.com/v1/spectroclusters/$PROVIDER?projectUid=$PROJECT_ID"' \
+curl --location "https://api.spectrocloud.com/v1/spectroclusters/$PROVIDER?projectUid=$PROJECT_ID" \
  --header 'Content-Type: application/json' \
  --header 'Accept: application/json' \
- --header "apiKey: $API_KEY"
+ --header "apiKey: $API_KEY" \
  --data  "$PAYLOAD"
 ```
 
@@ -1647,10 +1664,10 @@ export CLUSTER_ID="Your Cluster ID"
 <TabItem label="cURL" value="cluster-kubeconfig-curl">
 
 ```shell
- curl --location 'https://api.spectrocloud.com/v1/spectroclusters/$CLUSTER_ID/assets/kubeconfig' \
+ curl --location "https://api.spectrocloud.com/v1/spectroclusters/$CLUSTER_ID/assets/kubeconfig" \
  --header 'Accept: application/octet-stream' \
- --header 'projectUid: $PROJECT_ID' \
- --header 'apiKey: $API_KEY'
+ --header "projectUid: $PROJECT_ID" \
+ --header "apiKey: $API_KEY"
 ```
 
 </TabItem>

docs/docs-content/profiles/cluster-profiles/create-cluster-profiles/define-profile-variables.md

@@ -33,7 +33,7 @@ The following table describes the difference between profile variables and macro
 | Belongs to the tenant scope                                               |          ❌          |    ✅     |
 | Supports data format restrictions                                         |          ✅          |    ❌     |
 | Supports optionality restrictions                                         |          ✅          |    ❌     |
-| Supports [sprig template functions](https://masterminds.github.io/sprig/) |          ✅          |    ✅     |
+| Supports [sprig template functions](https://masterminds.github.io/sprig/) |          ❌          |    ✅     |
 
 This guide explains how you can define and manage cluster profile variables.
 

docs/docs-content/vertex/install-palette-vertex/install-on-vmware/airgap-install/environment-setup/vmware-vsphere-airgap-instructions.md

@@ -409,7 +409,7 @@ The default container runtime for OVAs is [Podman](https://podman.io/), not Dock
 
     You may encounter an error message during the OVA deployment stating unable to retrieve manifest or certificate.
     This is a known issue that was fixed in the
-    [VMware vCenter Server 7.0 Update 3q](https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3q-release-notes/index.html).
+    [VMware vCenter Server 7.0 Update 3q](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-releases/vsphere-vcenter-server-70u3q-release-notes.html).
     Reach out to [Broadcom Support](https://support.broadcom.com) if you need further guidance.
 
     :::

docs/docs-content/vm-management/vm-migration-assistant/create-migration-plans.md

@@ -78,7 +78,7 @@ Follow this guide to create migration plans using the VM Migration Assistant.
 - The <VersionedLink text="Virtual Machine Migration Assistant" url="/integrations/packs/?pack=vm-migration-assistant-pack"/> pack must be added to your cluster profile. Refer to [Create a VM Migration Assistant Cluster Profile](./create-vm-migration-assistant-profile.md) for guidance.
   - The VM Migration Assistant service console must be accessible from a web browser.
 
-- We recommend using a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) to uninstall [VMware Tools](https://docs.vmware.com/en/VMware-Tools/index.html), and install the [QEMU Guest Agent](https://wiki.qemu.org/Features/GuestAgent) and [VirtiIO drivers](https://github.com/virtio-win/kvm-guest-drivers-windows) on your migrated VMs. Installing the QEMU agent and Virtio drivers enhances compatibility with [KVM](https://linux-kvm.org/page/Main_Page), and enables advanced features like live migration and accurate reporting of guest status.
+- We recommend using a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) to uninstall [VMware Tools](https://docs.vmware.com/en/VMware-Tools/index.html), and install the [QEMU Guest Agent](https://wiki.qemu.org/Features/GuestAgent) and [VirtiIO drivers](https://github.com/virtio-win/kvm-guest-drivers-windows) on your migrated VMs. Installing the QEMU agent and Virtio drivers enhances compatibility with VMO, and enables advanced features like live migration and accurate reporting of guest status.
 
   You can provide [virt-customize](https://github.com/kubev2v/forklift/commit/650d73d2308d73fe596666a2f097aefda32845f6) scripts inside a ConfigMap to automatically perform these actions on your VMs during migration. The ConfigMap must exist in your target namespace before migrating your VMs.
 

docs/docs-content/vm-management/vm-migration-assistant/create-source-providers.md

@@ -27,57 +27,16 @@ Machines (VMs) that need to be migrated.
 
   - The VMO cluster must have network connectivity to vCenter and ESXi hosts, and the VMs you want to migrate.
 
-  :::warning
-
-  If you need to provision `Block` storage volumes during the VM migration process, add the following custom
-  configuration to your VMO cluster OS pack. Applying this configuration may cause a cluster repave. For more
-  information, refer to
-  [Repave Behaviors and Configurations](../../clusters/cluster-management/node-pool.md#repave-behavior-and-configuration)
-
-  Additionally, we recommend provisioning volumes with the `ReadWriteMany` access mode to ensure that VMs can be
-  [live migrated](https://kubevirt.io/user-guide/compute/live_migration/#limitations).
-
-  ```yaml
-  kubeadmconfig:
-     preKubeadmCommands:
-        # Start containerd with new configuration
-        - systemctl daemon-reload
-        - systemctl restart containerd
-     files:
-        - targetPath: /etc/containerd/config.toml
-        targetOwner: "root:root"
-        targetPermissions: "0644"
-        content: |
-           ## template: jinja
-
-           # Use config version 2 to enable new configuration fields.
-           version = 2
-
-           imports = ["/etc/containerd/conf.d/*.toml"]
-
-           [plugins]
-              [plugins."io.containerd.grpc.v1.cri"]
-              sandbox_image = "registry.k8s.io/pause:3.9"
-              device_ownership_from_security_context = true
-              [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]
-              runtime_type = "io.containerd.runc.v2"
-              [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]
-              SystemdCgroup = true
-  ```
-
-  :::
-
 - A vCenter user account with the following necessary privileges to perform migrations.
 
   | **Privileges**                                      | **Description**                   |
   |----------------------------------------------------|------------------------------------------------------------------------------------------------------------------------|
-  | **[Virtual machine.Interaction.Power Off](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-3D47149A-947D-4608-88B3-E5811129EFA8.html)**             | Allows shutting down a powered-on virtual machine, powering down its guest operating system.    |
-  | **[Virtual machine.Interaction.Power On](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-3D47149A-947D-4608-88B3-E5811129EFA8.html)**              | Enables starting a powered-off virtual machine or resuming a suspended one.                              |
-  | [**Virtual Machine Interaction Privileges** (all)](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-3D47149A-947D-4608-88B3-E5811129EFA8.html) | Allow creating, cloning, modifying, customizing, and managing templates, virtual machines, their files, and customization specifications, as well as performing disk and deployment-related operations. | 
-  | **[Virtual machine.Snapshot management.Create snapshot](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-222FE721-0968-4E9E-9F98-7CB03E7185E8.html)** | Allows capturing the current state of a virtual machine as a snapshot.  |
-  | **[Virtual machine.Snapshot management.Remove Snapshot](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.security.doc/GUID-222FE721-0968-4E9E-9F98-7CB03E7185E8.html)** | Permits deletion of a snapshot from the snapshot history.    |
+  | [**Virtual Machine Interaction Privileges** (all)](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges/virtual-machine-interaction-privileges.html) | Allow creating, cloning, modifying, customizing, and managing templates, virtual machines, their files, and customization specifications, as well as performing disk and deployment-related operations. |
+  | **[Virtual machine.Snapshot management.Create snapshot](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges/virtual-machine-snapshot-management-privileges.html)** | Allows capturing the current state of a virtual machine as a snapshot.  |
+  | **[Virtual machine.Snapshot management.Remove Snapshot](https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/8-0/vsphere-security-8-0/defined-privileges/virtual-machine-snapshot-management-privileges.html)** | Permits deletion of a snapshot from the snapshot history.    |
 
   - Migrations can be optionally accelerated by providing credentials for the ESXi hosts where the VMs reside.
+
 - One or more VMs hosted in VMware vSphere. Only VMs whose operating systems are included under
   [`virt-v2v` supported guest systems](https://libguestfs.org/virt-v2v-support.1.html) can be migrated.