stacktape 3.5.8 → 3.6.0

package/.tsconfig.bun-build.json

@@ -0,0 +1 @@
+{"extends":"/home/runner/work/stacktape/stacktape/tsconfig.json","compilerOptions":{"jsx":"preserve","jsxImportSource":"react","customConditions":[]}}

package/ai-docs/cli-ref/aws-profile-create.md

@@ -0,0 +1,22 @@
+---
+docType: cli-ref
+title: "CLI: aws-profile:create"
+tags:
+  - aws-profile:create
+  - aws-profile
+  - create
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape aws-profile:create`
+
+Creates a new AWS profile on your system.
+
+You will be prompted to enter a profile name, AWS Access Key ID, and AWS Secret Access Key. The credentials are stored in the default AWS location in your home directory and can be used by other AWS tools.
+
+## Usage
+
+```bash
+stacktape aws-profile:create
+```

package/ai-docs/cli-ref/aws-profile-delete.md

@@ -0,0 +1,22 @@
+---
+docType: cli-ref
+title: "CLI: aws-profile:delete"
+tags:
+  - aws-profile:delete
+  - aws-profile
+  - delete
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape aws-profile:delete`
+
+Deletes an AWS profile from your system.
+
+You will be prompted to enter the name of the profile to delete.
+
+## Usage
+
+```bash
+stacktape aws-profile:delete
+```

package/ai-docs/cli-ref/aws-profile-list.md

@@ -0,0 +1,20 @@
+---
+docType: cli-ref
+title: "CLI: aws-profile:list"
+tags:
+  - aws-profile:list
+  - aws-profile
+  - list
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape aws-profile:list`
+
+Lists all AWS profiles configured on your system.
+
+## Usage
+
+```bash
+stacktape aws-profile:list
+```

package/ai-docs/cli-ref/aws-profile-update.md

@@ -0,0 +1,22 @@
+---
+docType: cli-ref
+title: "CLI: aws-profile:update"
+tags:
+  - aws-profile:update
+  - aws-profile
+  - update
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape aws-profile:update`
+
+Updates an existing AWS profile on your system.
+
+You will be prompted to enter the profile name and the new credentials.
+
+## Usage
+
+```bash
+stacktape aws-profile:update
+```

package/ai-docs/cli-ref/bastion-session.md

@@ -0,0 +1,29 @@
+---
+docType: cli-ref
+title: "CLI: bastion:session"
+tags:
+  - bastion:session
+  - bastion
+  - session
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape bastion:session`
+
+Starts an interactive session with a bastion host.
+
+Your stack must include a `bastion` resource. If you have multiple bastions, you can specify which one to connect to with the `--bastionResource` argument. The session is established over a secure SSM connection.
+
+For more information, refer to the [bastion documentation](https://docs.stacktape.com/bastion-servers/#connecting-to-bastion-interactive-session).
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+
+## Usage
+
+```bash
+stacktape bastion:session --region <value> --stage <value>
+```

package/ai-docs/cli-ref/bastion-tunnel.md

@@ -0,0 +1,30 @@
+---
+docType: cli-ref
+title: "CLI: bastion:tunnel"
+tags:
+  - bastion:tunnel
+  - bastion
+  - tunnel
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape bastion:tunnel`
+
+Creates a secure tunnel to a resource through a bastion host.
+
+Your stack must include a `bastion` resource. This is useful for accessing resources in a private VPC. If you have multiple bastions, you can specify one with the `--bastionResource` argument. The command will print the tunneled endpoints to the terminal.
+
+For more information, refer to the [bastion tunnel documentation](https://docs.stacktape.com/bastion-servers/#creating-bastion-tunnel).
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape bastion:tunnel --region <value> --stage <value> --resourceName <value>
+```

package/ai-docs/cli-ref/bucket-sync.md

@@ -0,0 +1,30 @@
+---
+docType: cli-ref
+title: "CLI: bucket:sync"
+tags:
+  - bucket:sync
+  - bucket
+  - sync
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape bucket:sync`
+
+Synchronizes the contents of a local directory with an S3 bucket.
+
+You can specify the bucket in two ways:
+- **Using Stacktape configuration:** Provide the `stage` and `resourceName`. Stacktape will identify the bucket from the deployed stack and sync the directory specified in the configuration file.
+- **Using bucket ID:** Provide a valid `bucketId` (AWS physical resource ID or bucket name) and a `sourcePath`.
+
+Files in the bucket that are not present in the source directory will be removed.
+
+## Required Arguments
+
+- `--region`
+
+## Usage
+
+```bash
+stacktape bucket:sync --region <value>
+```

package/ai-docs/cli-ref/cf-module-update.md

@@ -0,0 +1,26 @@
+---
+docType: cli-ref
+title: "CLI: cf-module:update"
+tags:
+  - cf-module:update
+  - cf-module
+  - update
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape cf-module:update`
+
+Updates AWS CloudFormation infrastructure module private types to the latest compatible version.
+
+AWS CloudFormation infrastructure modules are used to integrate third-party services into your stack. If a third-party API changes, use this command to update the modules in your account to the latest version.
+
+## Required Arguments
+
+- `--region`
+
+## Usage
+
+```bash
+stacktape cf-module:update --region <value>
+```

package/ai-docs/cli-ref/cf-rollback.md

@@ -0,0 +1,28 @@
+---
+docType: cli-ref
+title: "CLI: cf:rollback"
+tags:
+  - cf:rollback
+  - cf
+  - rollback
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape cf:rollback`
+
+Rolls back the CloudFormation stack to the last known good state.
+
+This is useful if a stack update fails and leaves the stack in an `UPDATE_FAILED` or `UPDATE_ROLLBACK_FAILED` state. This uses CloudFormation's native rollback mechanism.
+
+For rolling back to a specific previous deployment version, use `rollback` instead.
+
+## Required Arguments
+
+- `--region`
+
+## Usage
+
+```bash
+stacktape cf:rollback --region <value>
+```

package/ai-docs/cli-ref/codebuild-deploy.md

@@ -0,0 +1,34 @@
+---
+docType: cli-ref
+title: "CLI: codebuild:deploy"
+tags:
+  - codebuild:deploy
+  - codebuild
+  - deploy
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape codebuild:deploy`
+
+Deploys your stack to AWS using AWS CodeBuild.
+
+This command offloads the deployment process to a dedicated environment within your AWS account, which is useful for resource-intensive projects.
+
+Here's how it works:
+1. Your project is zipped and uploaded to an S3 bucket in your account.
+2. A CodeBuild environment (a dedicated VM) is provisioned.
+3. The deployment begins, and logs are streamed to your terminal in real-time.
+
+Like the `deploy` command, this requires a `stacktape.yml` file.
+
+## Required Arguments
+
+- `--stage`
+- `--region`
+
+## Usage
+
+```bash
+stacktape codebuild:deploy --stage <value> --region <value>
+```

package/ai-docs/cli-ref/compile-template.md

@@ -0,0 +1,25 @@
+---
+docType: cli-ref
+title: "CLI: compile-template"
+tags:
+  - compile-template
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape compile-template`
+
+Compiles your Stacktape configuration into a CloudFormation template.
+
+By default, the template is saved to `./compiled-template.yaml`. Use the `--outFile` option to specify a different path.
+
+## Required Arguments
+
+- `--stage`
+- `--region`
+
+## Usage
+
+```bash
+stacktape compile-template --stage <value> --region <value>
+```

package/ai-docs/cli-ref/container-session.md

@@ -0,0 +1,30 @@
+---
+docType: cli-ref
+title: "CLI: container:session"
+tags:
+  - container:session
+  - container
+  - session
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape container:session`
+
+Starts an interactive session inside a deployed container.
+
+The session is established using ECS Exec and a secure SSM connection. If your service has multiple containers, you can choose which one to connect to. This is useful for debugging and inspecting running containers.
+
+For more information, refer to the [container session documentation](https://docs.stacktape.com/bastion-servers/#connecting-to-bastion-interactive-session).
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape container:session --region <value> --stage <value> --resourceName <value>
+```

package/ai-docs/cli-ref/debug-alarms.md

@@ -0,0 +1,28 @@
+---
+docType: cli-ref
+title: "CLI: debug:alarms"
+tags:
+  - debug:alarms
+  - debug
+  - alarms
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:alarms`
+
+View CloudWatch alarm states for stack resources.
+
+Shows all alarms configured for the stack with their current state (OK, ALARM, INSUFFICIENT_DATA).
+Filter by resource name or alarm state.
+
+## Required Arguments
+
+- `--stage`
+- `--region`
+
+## Usage
+
+```bash
+stacktape debug:alarms --stage <value> --region <value>
+```

package/ai-docs/cli-ref/debug-aws-sdk.md

@@ -0,0 +1,33 @@
+---
+docType: cli-ref
+title: "CLI: debug:aws-sdk"
+tags:
+  - debug:aws-sdk
+  - debug
+  - aws-sdk
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:aws-sdk`
+
+Execute read-only AWS SDK commands against deployed resources.
+
+Provides direct access to AWS SDK v3 for inspecting deployed resources. Only read-only operations (List*, Get*, Describe*, Head*) are allowed.
+
+Examples:
+  stacktape debug:aws-sdk --stage prod --service lambda --command ListFunctions
+  stacktape debug:aws-sdk --stage prod --service dynamodb --command Scan --input '{"TableName": "my-table", "Limit": 10}'
+  stacktape debug:aws-sdk --stage prod --service logs --command FilterLogEvents --input '{"logGroupName": "/aws/lambda/my-func"}'
+
+## Required Arguments
+
+- `--region`
+- `--service`
+- `--command`
+
+## Usage
+
+```bash
+stacktape debug:aws-sdk --region <value> --service <value> --command <value>
+```

package/ai-docs/cli-ref/debug-container-exec.md

@@ -0,0 +1,36 @@
+---
+docType: cli-ref
+title: "CLI: debug:container-exec"
+tags:
+  - debug:container-exec
+  - debug
+  - container-exec
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:container-exec`
+
+Execute a command in a running container and return the output.
+
+Runs a command inside a deployed container workload (web-service, private-service, worker-service, or multi-container-workload) using ECS Exec. The command output is captured and returned as JSON.
+
+Use --taskArn to specify which task to connect to when multiple instances are running (defaults to first available). Use --container to specify which container for multi-container workloads.
+
+Examples:
+  stacktape debug:container-exec --stage prod --resourceName myService --command "ls -la"
+  stacktape debug:container-exec --stage prod --resourceName myService --command "cat /app/config.json"
+  stacktape debug:container-exec --stage prod --resourceName myService --taskArn abc123 --command "env"
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+- `--command`
+
+## Usage
+
+```bash
+stacktape debug:container-exec --region <value> --stage <value> --resourceName <value> --command <value>
+```

package/ai-docs/cli-ref/debug-dynamodb.md

@@ -0,0 +1,35 @@
+---
+docType: cli-ref
+title: "CLI: debug:dynamodb"
+tags:
+  - debug:dynamodb
+  - debug
+  - dynamodb
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:dynamodb`
+
+Query a deployed DynamoDB table.
+
+Supports operations: scan, query, get, schema, sample. All operations are read-only.
+
+Examples:
+  stacktape debug:dynamodb --stage prod --resourceName myTable --operation sample
+  stacktape debug:dynamodb --stage prod --resourceName myTable --operation schema
+  stacktape debug:dynamodb --stage prod --resourceName myTable --operation scan --limit 50
+  stacktape debug:dynamodb --stage prod --resourceName myTable --operation query --pk '{"userId": "123"}'
+  stacktape debug:dynamodb --stage prod --resourceName myTable --operation get --pk '{"userId": "123"}' --sk '{"timestamp": 1234}'
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape debug:dynamodb --region <value> --stage <value> --resourceName <value>
+```

package/ai-docs/cli-ref/debug-logs.md

@@ -0,0 +1,34 @@
+---
+docType: cli-ref
+title: "CLI: debug:logs"
+tags:
+  - debug:logs
+  - debug
+  - logs
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:logs`
+
+Fetch and analyze logs from a deployed resource.
+
+Supports two modes:
+- **Standard**: Fetches recent log events with optional filtering
+- **Insights**: Runs CloudWatch Logs Insights query with --query flag
+
+Examples:
+  stacktape debug:logs --stage prod --resourceName myLambda --startTime "1h"
+  stacktape debug:logs --stage prod --resourceName myLambda --query "fields @timestamp, @message | filter @message like /ERROR/"
+
+## Required Arguments
+
+- `--stage`
+- `--region`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape debug:logs --stage <value> --region <value> --resourceName <value>
+```

package/ai-docs/cli-ref/debug-metrics.md

@@ -0,0 +1,33 @@
+---
+docType: cli-ref
+title: "CLI: debug:metrics"
+tags:
+  - debug:metrics
+  - debug
+  - metrics
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:metrics`
+
+Fetch CloudWatch metrics for a deployed resource.
+
+Supported metrics by resource type:
+- Lambda: Invocations, Errors, Duration, Throttles
+- ECS: CPUUtilization, MemoryUtilization
+- RDS: CPUUtilization, DatabaseConnections, FreeStorageSpace
+- API Gateway: Count, 4XXError, 5XXError, Latency
+
+## Required Arguments
+
+- `--stage`
+- `--region`
+- `--resourceName`
+- `--metric`
+
+## Usage
+
+```bash
+stacktape debug:metrics --stage <value> --region <value> --resourceName <value> --metric <value>
+```

package/ai-docs/cli-ref/debug-opensearch.md

@@ -0,0 +1,35 @@
+---
+docType: cli-ref
+title: "CLI: debug:opensearch"
+tags:
+  - debug:opensearch
+  - debug
+  - opensearch
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:opensearch`
+
+Query a deployed OpenSearch domain.
+
+Supports operations: search, get, indices, mapping, count. All operations are read-only.
+
+Examples:
+  stacktape debug:opensearch --stage prod --resourceName mySearch --operation indices
+  stacktape debug:opensearch --stage prod --resourceName mySearch --operation mapping --index users
+  stacktape debug:opensearch --stage prod --resourceName mySearch --operation count --index users
+  stacktape debug:opensearch --stage prod --resourceName mySearch --operation get --index users --id doc123
+  stacktape debug:opensearch --stage prod --resourceName mySearch --operation search --query '{"match_all": {}}'
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape debug:opensearch --region <value> --stage <value> --resourceName <value>
+```

package/ai-docs/cli-ref/debug-redis.md

@@ -0,0 +1,36 @@
+---
+docType: cli-ref
+title: "CLI: debug:redis"
+tags:
+  - debug:redis
+  - debug
+  - redis
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:redis`
+
+Query a deployed Redis cluster.
+
+Supports operations: keys, get, ttl, info, type. All operations are read-only.
+
+If the Redis cluster is VPC-only, use --bastionResource to tunnel through a bastion host.
+
+Examples:
+  stacktape debug:redis --stage prod --resourceName myRedis --operation info
+  stacktape debug:redis --stage prod --resourceName myRedis --operation keys --pattern "user:*"
+  stacktape debug:redis --stage prod --resourceName myRedis --operation get --key "session:abc123"
+  stacktape debug:redis --stage prod --resourceName myRedis --bastionResource myBastion --operation info
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+
+## Usage
+
+```bash
+stacktape debug:redis --region <value> --stage <value> --resourceName <value>
+```

package/ai-docs/cli-ref/debug-sql.md

@@ -0,0 +1,35 @@
+---
+docType: cli-ref
+title: "CLI: debug:sql"
+tags:
+  - debug:sql
+  - debug
+  - sql
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape debug:sql`
+
+Execute read-only SQL queries against a deployed relational database.
+
+Supports PostgreSQL and MySQL databases. Only read-only queries (SELECT, SHOW, DESCRIBE, EXPLAIN) are allowed.
+
+If the database is VPC-only, use --bastionResource to tunnel through a bastion host.
+
+Examples:
+  stacktape debug:sql --stage prod --resourceName myDatabase --sql "SELECT * FROM users LIMIT 10"
+  stacktape debug:sql --stage prod --resourceName myDatabase --bastionResource myBastion --sql "SHOW TABLES"
+
+## Required Arguments
+
+- `--region`
+- `--stage`
+- `--resourceName`
+- `--sql`
+
+## Usage
+
+```bash
+stacktape debug:sql --region <value> --stage <value> --resourceName <value> --sql <value>
+```

package/ai-docs/cli-ref/defaults-configure.md

@@ -0,0 +1,29 @@
+---
+docType: cli-ref
+title: "CLI: defaults:configure"
+tags:
+  - defaults:configure
+  - defaults
+  - configure
+source: src/config/cli/commands.ts
+priority: 3
+---
+
+# `stacktape defaults:configure`
+
+Sets system-wide default arguments for Stacktape commands.
+
+You can set defaults for:
+- `region`
+- `stage`
+- `awsProfile`
+- `projectName`
+- `awsAccount`
+
+You can also configure default executables for resolving Node.js directives.
+
+## Usage
+
+```bash
+stacktape defaults:configure
+```