Revert main back to 8b6254e: undo commits post that (#285)

* Revert main back to 8b6254e: undo commits post that

* fixing pre-commit

---------

Co-authored-by: Nupur Goyal <[email protected]>

Author: nupurg-ibm

.catalog-onboard-pipeline.yaml

@@ -22,23 +22,3 @@ offerings:
         region: us-south
       # pre_validation: tests/scripts/pre-validation.sh # optionally run a command before validation runs
       # post_validation: tests/scripts/post-validation.sh  # optionally run a command after validation completes
-- name: deploy-arch-ibm-storage-scale # must match the offering name in the ibm_catalog.json
-  kind: solution
-  catalog_id: 90717ada-be34-4b82-a0d9-0f225f8dbd76
-  offering_id: 33105573-84df-4279-9efa-48887456fa6d
-  # list all of the variations (flavors) you have included in the ibm_catalog.json
-  variations:
-    - name: Cluster-with-Scale
-      mark_ready: false # have pipeline mark as visible if validation passes
-      install_type: fullstack # ensure value matches what is in ibm_catalog.json (fullstack or extension)
-      destroy_resources_on_failure: false # defaults to false if not specified so resources can be inspected to debug failures during validation
-      destroy_workspace_on_failure: false # defaults to false if not specified so schematics workspace can be inspected to debug failures during validation
-      import_only: false  # defaults to false - set to true if you do not want to do any validation, but be aware offering can't be publish if not validated
-      validation_rg: validation # the resource group in which to do validation in. Will be created if does not exist. If not specified, default value is 'validation'
-      # scc details needed if your offering is claiming any compliance controls
-      scc:
-        # must be an instance in the same account the validation is being done in
-        instance_id: 1c7d5f78-9262-44c3-b779-b28fe4d88c37
-        region: us-south
-      # pre_validation: tests/scripts/pre-validation.sh # optionally run a command before validation runs
-      # post_validation: tests/scripts/post-validation.sh  # optionally run a command after validation completes

.secrets.baseline

@@ -3,7 +3,7 @@
     "files": "^.secrets.baseline$",
     "lines": null
   },
-  "generated_at": "2025-09-29T12:05:07Z",
+  "generated_at": "2025-06-19T07:38:57Z",
   "plugins_used": [
     {
       "name": "AWSKeyDetector"
@@ -102,152 +102,6 @@
         "type": "Secret Keyword",
         "verified_result": null
       }
-    ],
-    "samples/configs/scale_catalog_values.json": [
-      {
-        "hashed_secret": "2e7ec5f9611439242fd8e30e3e13bc36baff526c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 10,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "1f5e25be9b575e9f5d39c82dfd1d9f4d73f1975c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 45,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "b295b04949a98dc50ba65adcddd588077b93ab3c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 62,
-        "type": "Secret Keyword",
-        "verified_result": null
-      }
-    ],
-    "tools/minimal-demo-prod-scripts/README.md": [
-      {
-        "hashed_secret": "89a6cfe2a229151e8055abee107d45ed087bbb4f",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 28,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "365b78d42089abe4583503eded60fa7c1b3e1cd0",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 47,
-        "type": "Secret Keyword",
-        "verified_result": null
-      }
-    ],
-    "tools/minimal-demo-prod-scripts/catalog_values_demo_deployment.json": [
-      {
-        "hashed_secret": "216168000275f83a7bc3599e708c5bafab959783",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 2,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "55aac310878e11ce14b29027f77e58cb7c4fe7a4",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 8,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "1f5e25be9b575e9f5d39c82dfd1d9f4d73f1975c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 56,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "b295b04949a98dc50ba65adcddd588077b93ab3c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 65,
-        "type": "Secret Keyword",
-        "verified_result": null
-      }
-    ],
-    "tools/minimal-demo-prod-scripts/catalog_values_minimal_deployment.json": [
-      {
-        "hashed_secret": "216168000275f83a7bc3599e708c5bafab959783",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 2,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "55aac310878e11ce14b29027f77e58cb7c4fe7a4",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 8,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "1f5e25be9b575e9f5d39c82dfd1d9f4d73f1975c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 56,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "b295b04949a98dc50ba65adcddd588077b93ab3c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 65,
-        "type": "Secret Keyword",
-        "verified_result": null
-      }
-    ],
-    "tools/minimal-demo-prod-scripts/catalog_values_production_deployment.json": [
-      {
-        "hashed_secret": "216168000275f83a7bc3599e708c5bafab959783",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 2,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "55aac310878e11ce14b29027f77e58cb7c4fe7a4",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 8,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "1f5e25be9b575e9f5d39c82dfd1d9f4d73f1975c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 56,
-        "type": "Secret Keyword",
-        "verified_result": null
-      },
-      {
-        "hashed_secret": "b295b04949a98dc50ba65adcddd588077b93ab3c",
-        "is_secret": true,
-        "is_verified": false,
-        "line_number": 65,
-        "type": "Secret Keyword",
-        "verified_result": null
-      }
     ]
   },
   "version": "0.13.1+ibm.62.dss",

.tekton/hpcaas/hpcaas-pr-pipeline/hpcaas-pipeline-git-pr-status.yaml

@@ -61,7 +61,7 @@ spec:
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
     - name: cluster_name
-      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifier for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
+      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
       description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).

.tekton/hpcaas/hpcaas-pr-pipeline/listener-git-pr-status.yaml

@@ -56,7 +56,7 @@ spec:
       description: Name of the custom image that you want to use to create virtual server instances in your IBM Cloud account to deploy the IBM Cloud HPC cluster management nodes. By default, the solution uses a RHEL88 base image with additional software packages mentioned [here](https://cloud.ibm.com/docs/ibm-spectrum-lsf#create-custom-image). If you would like to include your application-specific binary files, follow the instructions in [ Planning for custom images ](https://cloud.ibm.com/docs/vpc?topic=vpc-planning-custom-images) to create your own custom image and use that to build the IBM Cloud HPC cluster through this offering.
       default: ""
     - name: cluster_name
-      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifier for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
+      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: reservation_id
       description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
@@ -65,7 +65,7 @@ spec:
       default: ""
       description: The IBM Cloud zone name within the selected region where the IBM Cloud HPC cluster should be deployed and requires a single zone input value. Supported zones are eu-de-2 and eu-de-3 for eu-de, us-east-1 and us-east-3 for us-east, and us-south-1 for us-south. The management nodes, file storage shares, and compute nodes will be deployed in the same zone.[Learn more](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region#get-zones-using-the-cli).
     - name: us_east_cluster_id
-      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifier for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
+      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: us_east_reservation_id
       description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
@@ -74,7 +74,7 @@ spec:
       default: ""
       description: The IBM Cloud zone name within the selected region where the IBM Cloud HPC cluster should be deployed and requires a single zone input value. Supported zones are eu-de-2 and eu-de-3 for eu-de, us-east-1 and us-east-3 for us-east, and us-south-1 for us-south. The management nodes, file storage shares, and compute nodes will be deployed in the same zone.[Learn more](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region#get-zones-using-the-cli).
     - name: eu_de_cluster_id
-      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifier for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
+      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: eu_de_reservation_id
       description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).
@@ -83,7 +83,7 @@ spec:
       default: ""
       description: The IBM Cloud zone name within the selected region where the IBM Cloud HPC cluster should be deployed and requires a single zone input value. Supported zones are eu-de-2 and eu-de-3 for eu-de, us-east-1 and us-east-3 for us-east, and us-south-1 for us-south. The management nodes, file storage shares, and compute nodes will be deployed in the same zone.[Learn more](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region#get-zones-using-the-cli).
     - name: us_south_cluster_id
-      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifier for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
+      description: Ensure that you have received the cluster ID from IBM technical sales. A unique identifer for HPC cluster used by IBM Cloud HPC to differentiate different HPC clusters within the same reservation. This can be up to 39 alphanumeric characters including the underscore (_), the hyphen (-), and the period (.) characters. You cannot change the cluster ID after deployment.
       default: ""
     - name: us_south_reservation_id
       description: Ensure that you have received the reservation ID from IBM technical sales. Reservation ID is a unique identifier to distinguish different IBM Cloud HPC service agreements. It must start with a letter and can only contain letters, numbers, hyphens (-), or underscores (_).