Cloud SDK

Developer workflow automation tool for project lifecycle management. Provides commands for initializing projects, running checks, building, testing, deploying, managing configuration, generating templates, producing documentation, and cleaning build artifacts — all from a single CLI interface.

Commands

Data Storage

All operational data is stored in ~/.local/share/cloud-sdk/ by default. You can override this by setting the CLOUD_SDK_DIR environment variable. Key files inside the data directory:

• - history.log — timestamped log of every command executed
• INLINECODE16 — project-level configuration (managed via config command)

The tool respects XDG_DATA_HOME if set, falling back to $HOME/.local/share.

Requirements

• - Bash 4.0+ (uses set -euo pipefail for strict error handling)
• coreutils (standard date, mkdir, echo)
• No external dependencies or API keys required
• Works on Linux and macOS out of the box

When to Use

1. 1. Bootstrapping a new project — run cloud-sdk init to set up project scaffolding quickly from the terminal without remembering per-tool init commands
2. Pre-commit quality gates — use cloud-sdk check as part of a Git pre-commit hook to run lint + type-check + tests before every commit
3. CI/CD pipeline steps — chain cloud-sdk build and cloud-sdk test inside your continuous integration scripts for a consistent, tool-agnostic interface
4. Deployment checklists — run cloud-sdk deploy to get a guided walkthrough of the build → test → stage → prod pipeline so nothing gets skipped
5. Housekeeping and cleanup — execute cloud-sdk clean to wipe build artifacts after releases, freeing disk space and resetting state

Examples

CODEBLOCK0

Configuration

Set the CLOUD_SDK_DIR environment variable to change the data directory:

CODEBLOCK1

Default location: INLINECODE31

Output

All command output goes to stdout. Redirect to a file if needed:

CODEBLOCK2

History is automatically logged to $DATA_DIR/history.log with timestamps.