use sticky disk grpc port from the env if possible

.github/workflows/basic.yaml

@@ -0,0 +1,76 @@
+name: Basic Sticky Disk Test
+on:
+  workflow_dispatch:
+  pull_request:
+
+jobs:
+  test-sticky-disk:
+    name: Test Sticky Disk
+    runs-on: blacksmith
+    strategy:
+      matrix:
+        iteration: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
+      fail-fast: false
+    steps:
+      - name: Create directory called
+        run: sudo mkdir -p ./shouldseethis
+
+      - name: Mount First Sticky Disk
+        uses: useblacksmith/stickydisk@main
+        with:
+          key: foo
+          path: ./shouldseethis
+
+      - name: List first directory if exists
+        run: |
+          if [ -d "./shouldseethis" ]; then
+            ls -la ./shouldseethis
+          fi
+
+      - name: Write test file to first disk
+        run: sudo sh -c 'echo "Hello from first sticky disk" > ./shouldseethis/test.txt'
+
+      - name: Mount Second Sticky Disk
+        uses: useblacksmith/stickydisk@main
+        with:
+          key: bar
+          path: ./seconddisk
+
+      - name: List second directory if exists
+        run: |
+          if [ -d "./seconddisk" ]; then
+            ls -la ./seconddisk
+          fi
+
+      - name: Write test file to second disk
+        run: sudo sh -c 'echo "Hello from second sticky disk" > ./seconddisk/test.txt'
+
+      - name: Mount Third Sticky Disk
+        uses: useblacksmith/stickydisk@main
+        with:
+          key: baz
+          path: ./thirddisk
+
+      - name: List third directory if exists
+        run: |
+          if [ -d "./thirddisk" ]; then
+            ls -la ./thirddisk
+          fi
+
+      - name: Write test file to third disk
+        run: sudo sh -c 'echo "Hello from third sticky disk" > ./thirddisk/test.txt'
+
+      - name: Mount First Sticky Disk Again
+        uses: useblacksmith/stickydisk@main
+        with:
+          key: foo
+          path: ./shouldseethis_again
+
+      - name: List first directory again if exists
+        run: |
+          if [ -d "./shouldseethis_again" ]; then
+            ls -la ./shouldseethis_again
+          fi
+
+      - name: Write test file to first disk again
+        run: sudo sh -c 'echo "Hello again from first sticky disk" > ./shouldseethis_again/test2.txt'

.github/workflows/build.yaml

@@ -17,6 +17,15 @@ jobs:
         with:
           node-version-file: .nvmrc
 
+      - name: Setup Buf
+        uses: bufbuild/buf-setup-action@v1
+
+      - name: Configure Buf Registry
+        run: |
+          npm config set @buf:registry https://buf.build/gen/npm/v1/
+          npm config set //buf.build/gen/npm/v1/:_authToken ${{ secrets.BUF_TOKEN }}
+          npm install @buf/blacksmith_vm-agent.connectrpc_es@latest
+
       - name: Install Dependencies
         run: npm ci
 
@@ -26,4 +35,9 @@ jobs:
       - name: Build Action
         run: |
           npm run build
-          git diff && git diff-index --quiet --exit-code HEAD
+          # Check if any files were changed during build
+          if ! git diff --quiet; then
+            echo "Error: Build generated changes that aren't committed. Please run 'npm run build' locally and commit the changes."
+            git diff
+            exit 1
+          fi

.github/workflows/bump-tag.yaml

@@ -0,0 +1,22 @@
+name: Bump Tag
+
+on:
+  workflow_dispatch:
+
+jobs:
+  bump-tag:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+          ref: main
+
+      - name: Bump v1 tag
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "41898282+github-actions[bot]@users.noreply.github.com"
+          git tag -f v1
+          git push origin v1 -f

.gitignore

@@ -3,4 +3,27 @@
 !.git*
 !.nvmrc
 
+# Dependencies
 node_modules/
+
+# TypeScript
+*.tsbuildinfo
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Test coverage
+coverage/
+
+# Logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

README.md

@@ -1,76 +1,93 @@
-# Blacksmith Cache Delete Action
+<p align="center">
+  <picture>
+    <!-- Dark mode -->
+    <source media="(prefers-color-scheme: dark)" srcset="./Blacksmith_Logo-White-Large.png" width="300">
+    <!-- Light mode -->
+    <source media="(prefers-color-scheme: light)" srcset="./Blacksmith_Logo-Black-Large.png" width="300">
+    <img alt="Blacksmith Logo" src="./Blacksmith_Logo-Black-Large.png" width="300">
+  </picture>
+</p>
 
-A GitHub Action to delete caches from Blacksmith's cache storage. This action allows you to delete either a specific cache version or all versions of a cache key. This action only works Blacksmith runners.
+A GitHub Action that helps persist state written to disk across jobs. This action can serve as a superior alternative to the [Actions cache](https://github.com/useblacksmith/cache), especially when the cache artifacts are extremely large. Each sticky disk is hot-loaded into the runner and mounted at the specified path.
+The sticky disk is formatted as an ext4 filesystem.
 
-## Usage
+# Architecture
 
-```yaml
-- name: Delete Cache
-  uses: useblacksmith/cache-delete@v1
-  with:
-    key: Linux-composer-ecf6e2e236589e4d34ba89662b6bc2afe8e15237cd19a13df9dc0cb599ff4826
-    version: v213asda2cf # Optional: specific version to delete
-```
-
-## Inputs
+<p align="center">
+  <picture>
+    <!-- Dark mode -->
+    <source media="(prefers-color-scheme: dark)" srcset="./arch-dark-mode.png" width="1000">
+    <!-- Light mode -->
+    <source media="(prefers-color-scheme: light)" srcset="./arch-light.png" width="1000">
+    <img alt="Blacksmith Logo" src="./arch-light.png" width="1000">
+  </picture>
+</p>
 
-| Input     | Description                             | Required | Default |
-| --------- | --------------------------------------- | -------- | ------- |
-| `key`     | The cache key to delete                 | No\*     | -       |
-| `version` | Specific version of the cache to delete | No       | -       |
-| `prefix`  | Treat key as a prefix for bulk deletion | No       | false   |
+Blacksmith stores sticky disk artifacts in a secure, highly performant Ceph cluster, running on local NVMe drives. Our runners proxy their requests through our Storage Agents to interact with the Ceph cluster. Each sticky disk is uniquely identified by a key. When a GitHub Action job requests a sticky disk, the last committed snapshot will be cloned and mounted into the runner at the specified path. Once the job completes, the sticky disk will be unmounted and committed for future invocations. At the moment, customers can use up to 5 sticky disks in a single GitHub Action job.
 
-\* Required unless `prefix` is true, in which case it can be empty to match all cache keys
+# Use Cases
 
-## Examples
-
-### Delete All Versions of a Cache
-
-```yaml
-- name: Delete All Cache Versions
-  uses: useblacksmith/cache-delete@v1
-  with:
-    key: npm-cache
-```
+## NPM Package Caching
 
-### Delete a Specific Cache Version
+Node.js projects can have extensive dependency trees, leading to large `node_modules` directories. Sticky disks provide persistent, high-performance storage for your NPM packages.
 
 ```yaml
-- name: Delete Specific Cache Version
-  uses: useblacksmith/cache-delete@v1
-  with:
-    key: npm-cache
-    version: v1.0
+jobs:
+  build:
+    runs-on: blacksmith
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: useblacksmith/setup-node@v5
+        with:
+          node-version: '18.x'
+
+      - name: Mount NPM Cache
+        uses: useblacksmith/stickydisk@v1
+        with:
+          key: ${{ github.repository }}-npm-cache
+          path: ~/.npm
+
+      - name: Mount node_modules
+        uses: useblacksmith/stickydisk@v1
+        with:
+          key: ${{ github.repository }}-node-modules
+          path: ./node_modules
+
+      - name: Install Dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build
 ```
 
-### Delete All Caches with a Prefix
-
-```yaml
-- name: Delete All npm Caches
-  uses: useblacksmith/cache-delete@v1
-  with:
-    key: npm-
-    prefix: true
-```
+## Bazel Build Caching
 
-### Delete All Caches
+Bazel's remote cache can significantly improve build times, but uploading and downloading cached artifacts can still be a bottleneck. Using sticky disks with Blacksmith runners provides near-instant access to your Bazel caches as they are bind mounted into your runners on demand. Our [`useblacksmith/setup-bazel@v2`](https://github.com/useblacksmith/setup-bazel) action is a zero-confg way to use sticky disks to store the disk, repository, and external cache.
 
 ```yaml
-- name: Delete All Caches
-  uses: useblacksmith/cache-delete@v1
-  with:
-    key: ""
-    prefix: true
+jobs:
+  build:
+    runs-on: blacksmith
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Setup Bazel
+        uses: useblacksmith/setup-bazel@v2
+        with:
+          version: '6.x'
+
+      - name: Build
+        run: |
+          bazel build //...
 ```
 
-## Error Handling
-
-The action will:
-
-- Fail if the cache deletion request fails (non-404 error)
-- Log a message if the cache is not found (404)
-- Successfully complete if the cache is deleted
+### Cache Performance Comparison
 
-## License
+| Caching Solution | Cache Size | Average Download Speed | Time to Access |
+|-----------------|------------|----------------|----------------|
+| GitHub Actions Cache | 6GB | 90 MB/s | ~1m6s |
+| Blacksmith Cache | 6GB | 400 MB/s | ~15s |
+| Sticky Disks | 6GB | N/A | 3 seconds |
 
-This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

action.yml

@@ -1,20 +1,17 @@
-name: "Delete Blacksmith Cache"
-author: Aayush Shah
-description: "Deletes a cache or specific cache version from Blacksmith"
+name: "Blacksmith Sticky Disk"
+author: Aditya Maru
+description: "Creates a sticky disk on Blacksmith"
 branding:
   icon: folder-plus
   color: black
 inputs:
   key:
-    description: "The cache key to delete"
-    required: false
-  version:
-    description: "Specific version of the cache to delete (optional)"
-    required: false
-  prefix:
-    description: "Treat key as a prefix for bulk deletion"
-    required: false
-    default: "false"
+    description: "A unique key to identify the sticky disk"
+    required: true
+  path:
+    description: "The path at which to mount the sticky disk"
+    required: true
 runs:
   using: "node20"
   main: "dist/index.js"
+  post: "dist/post/index.js"