Skip to content

feat(cloud): add Linode / Akamai cloud adapter#405

Closed
ericaai-cyber wants to merge 4 commits into
profullstack:masterfrom
ericaai-cyber:feat/cloud-linode
Closed

feat(cloud): add Linode / Akamai cloud adapter#405
ericaai-cyber wants to merge 4 commits into
profullstack:masterfrom
ericaai-cyber:feat/cloud-linode

Conversation

@ericaai-cyber
Copy link
Copy Markdown
Contributor

What this adds

A cloud/linode adapter for Linode (now Akamai Cloud Computing), which is listed in the README under the Cloud infra section but currently has no package implementation.

Linode is one of the original VPS providers — affordable, straightforward, and recently rebranded as Akamai Cloud Computing. It offers shared VPS (Nanode, Standard), dedicated CPU, GPU (RTX 6000), block storage (Volumes), managed databases, and object storage. This fills a notable gap in cloud adapter coverage alongside DigitalOcean and Vultr.

Implementation details

  • Uses defineCloud from @profullstack/sh1pt-core, matching cloud/vultr, cloud/hetzner, and cloud/digitalocean adapters
  • Supports cpu-vps, gpu, bare-metal, block-storage, and managed-db instance kinds
  • Quote before provision — fetches Linode types and picks the cheapest match by region, respecting maxHourlyPrice guardrails
  • Region-aware: defaults to us-east, configurable via config.defaultRegion (also supports us-central, us-west, eu-west, eu-central, ap-south, ap-northeast, ca-central)
  • Handles both Linode instances and Volumes (block storage) in list(), destroy(), and status() — same fallback pattern as Vultr/Hetzner
  • tokenSetup guides users through API token creation at cloud.linode.com
  • TypeScript compiles clean against tsconfig.base.json
  • Uses Linode API v4 at https://api.linode.com/v4 with Bearer token auth

Files

  • packages/cloud/linode/package.json
  • packages/cloud/linode/tsconfig.json
  • packages/cloud/linode/src/index.ts

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

8 similar comments
@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@ericaai-cyber
Copy link
Copy Markdown
Contributor Author

Same situation as #404pnpm install is failing because our branch needs a rebase onto latest master. I've enabled Allow edits by maintainers so the auto-rebase bot can push. The code changes (3 files) are clean and ready for review once CI passes.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

9 similar comments
@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@github-actions
Copy link
Copy Markdown

🤖 Auto-rebase: The branch was rebased successfully locally but could not be pushed to the fork. Please enable 'Allow edits from maintainers' in the PR settings, or rebase manually: git fetch upstream master && git rebase upstream/master.

@ralyodio ralyodio closed this May 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants