@btc-embedded/cdk-extensions 0.22.14 → 0.22.15

package/.jsii

@@ -8497,7 +8497,7 @@
   },
   "name": "@btc-embedded/cdk-extensions",
   "readme": {
-    "markdown": "# BTC Embedded CDK Extensions\n\n# @btc-embedded/cdk-extensions\n\nA collection of reusable AWS CDK (Cloud Development Kit) extensions and constructs for building cloud infrastructure with TypeScript.\n\n## Features\n\n- **CDK Constructs**: Includes ready-to-use constructs for API Gateway, Application Load Balancer, Cognito, VPC, DocumentDB, and more.\n- **ECS Service Extensions**: Provides ECS service extensions for advanced container orchestration.\n- **Utilities**: Common utilities and helpers for stack parameters, value imports, and configuration parsing.\n- **Modular Extensions**: Easily extend AWS resources with features like logging, OpenTelemetry, EFS, Cloud Map, and custom containers.\n\n## Installation\n\n```sh\nyarn install @btc-embedded/cdk-extensions\n```\n\n## Usage Example\n\n### Basic Usage\n\n```typescript\nimport { ApiGateway } from \"@btc-embedded/cdk-extensions\";\n\n// Use constructs and extensions in your CDK app\n```\n\n### Using ApplicationStack for Simplified Configuration\n\nFor application-level stacks that reference a base platform stack, use `ApplicationStack` to ensure consistent use of the base platform stack name:\n\n```typescript\nimport { ApplicationStack } from \"@btc-embedded/cdk-extensions\";\n\nexport class MyAppStack extends ApplicationStack {\n  constructor(scope: Construct, id: string) {\n    super(scope, id, {\n      basePlatformStackName: \"my-platform-stack\",\n      env: {\n        account: \"123456789012\",\n        region: \"eu-central-1\",\n      },\n    });\n\n    // Constructs and extensions automatically resolve the platform stack name\n    // No need to pass basePlatformStackName repeatedly\n  }\n}\n```\n\n### Config-Driven Deployments\n\nUse `createApplicationApp` for configuration-driven deployments:\n\n```typescript\nimport {\n  createApplicationApp,\n  ApplicationStack,\n} from \"@btc-embedded/cdk-extensions\";\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  env: z.object({ account: z.string(), region: z.string() }),\n  basePlatformStackName: z.string(),\n});\n\ncreateApplicationApp({\n  directory: \"./config\",\n  schema: configSchema,\n  createStack: (scope, config) => new MyAppStack(scope, \"MyApp\", config),\n});\n```\n\n## CLI Commands\n\n### catnip — Cloud Toolkit by the CAT Department\n\nThe `catnip` CLI tool provides commands for cloud infrastructure diagnostics and management.\n\n#### stack-diagnose\n\nDiagnose CloudFormation stack deployment failures.\n\n**Usage:**\n\n```bash\n# Auto-detect and diagnose the last failed stack\ncatnip stack-diagnose\n\n# Diagnose a specific stack\ncatnip stack-diagnose --stack-name my-stack\n\n# Customize log output and task inspection\ncatnip stack-diagnose --stack-name my-stack --tail 200 --tasks 10\n```\n\n**Description:**\n\nThe `stack-diagnose` command provides comprehensive diagnostics for failed CloudFormation stacks. If no stack name is provided, it automatically detects and diagnoses the last failed stack in your AWS account. The command displays:\n\n- **Stack Status**: Current CloudFormation stack status and reason for failure\n- **CloudFormation Events**: Recent stack events showing what failed during deployment\n- **ECS Diagnostics** (if applicable): If the stack contains ECS services, additional diagnostics are performed including:\n  - Service event history\n  - Recent stopped task logs\n  - Container output for troubleshooting\n\n**Options:**\n\n- `--stack-name <name>` — CloudFormation stack name (optional; auto-detects last failed stack if omitted)\n- `--stage <name>` — Filter stacks by stage name (e.g., 'prod', 'dev') when auto-detecting; only used if --stack-name is not provided\n- `--tail <n>` — Number of log lines to show per container (default: 100)\n- `--tasks <n>` — Number of recent stopped tasks to inspect (default: 5)\n- `--region <region>` — AWS region (uses AWS_DEFAULT_REGION / AWS_REGION environment variable if not specified)\n- `--profile <profile>` — AWS named profile for local development\n\n**Examples:**\n\n```bash\n# Quick diagnosis of last failed stack\ncatnip stack-diagnose\n\n# Auto-detect failed stack for a specific stage (useful when multiple stages in same account)\ncatnip stack-diagnose --stage prod\n\n# Diagnose specific stack with extended logging\ncatnip stack-diagnose --stack-name prod-api-stack --tail 500 --tasks 10\n\n# Use specific AWS profile and region\ncatnip stack-diagnose --profile my-profile --region eu-central-1\n```\n\n#### ecs-logs\n\nStream live logs from running ECS services in a CloudFormation stack.\n\n**Usage:**\n\n```bash\n# Stream logs from all ECS services in a stack\nnpx catnip ecs-logs --stack-name my-stack\n\n# Follow logs in real-time\nnpx catnip ecs-logs --stack-name my-stack --follow\n\n# Filter by service name and show last 50 lines\nnpx catnip ecs-logs --stack-name my-stack --tail 50 --service api\n\n# Raw JSON output (for piping to jq or pino-pretty)\nnpx catnip ecs-logs --stack-name my-stack --output raw\n\n# Pretty-printed JSON with colors\nnpx catnip ecs-logs --stack-name my-stack --output pretty\n```\n\n**Options:**\n\n- `--stack-name <name>` — CloudFormation stack name (required)\n- `--tail <n>` — Lines of history to show per container (default: 100)\n- `-f, --follow` — Keep polling for new log events\n- `--service <name>` — Filter services by name\n- `-o, --output <mode>` — Output mode: `text`, `raw`, or `pretty` (default: text)\n- `--region <region>` — AWS region\n- `--profile <profile>` — AWS profile\n\n## Documentation\n\n- [API Reference](./API.md)\n\n## License\n\nApache-2.0 © BTC Embedded Systems AG\n"
+    "markdown": "# BTC Embedded CDK Extensions\n\n# @btc-embedded/cdk-extensions\n\nA collection of reusable AWS CDK (Cloud Development Kit) extensions and constructs for building cloud infrastructure with TypeScript.\n\n## Features\n\n- **CDK Constructs**: Includes ready-to-use constructs for API Gateway, Application Load Balancer, Cognito, VPC, DocumentDB, and more.\n- **ECS Service Extensions**: Provides ECS service extensions for advanced container orchestration.\n- **Utilities**: Common utilities and helpers for stack parameters, value imports, and configuration parsing.\n- **Modular Extensions**: Easily extend AWS resources with features like logging, OpenTelemetry, EFS, Cloud Map, and custom containers.\n\n## Installation\n\n```sh\nyarn install @btc-embedded/cdk-extensions\n```\n\n## Usage Example\n\n### Basic Usage\n\n```typescript\nimport { ApiGateway } from \"@btc-embedded/cdk-extensions\";\n\n// Use constructs and extensions in your CDK app\n```\n\n### Using ApplicationStack for Simplified Configuration\n\nFor application-level stacks that reference a base platform stack, use `ApplicationStack` to ensure consistent use of the base platform stack name:\n\n```typescript\nimport { ApplicationStack } from \"@btc-embedded/cdk-extensions\";\n\nexport class MyAppStack extends ApplicationStack {\n  constructor(scope: Construct, id: string) {\n    super(scope, id, {\n      basePlatformStackName: \"my-platform-stack\",\n      env: {\n        account: \"123456789012\",\n        region: \"eu-central-1\",\n      },\n    });\n\n    // Constructs and extensions automatically resolve the platform stack name\n    // No need to pass basePlatformStackName repeatedly\n  }\n}\n```\n\n### Config-Driven Deployments\n\nUse `createApplicationApp` for configuration-driven deployments:\n\n```typescript\nimport {\n  createApplicationApp,\n  ApplicationStack,\n} from \"@btc-embedded/cdk-extensions\";\nimport { z } from \"zod\";\n\nconst configSchema = z.object({\n  env: z.object({ account: z.string(), region: z.string() }),\n  basePlatformStackName: z.string(),\n});\n\ncreateApplicationApp({\n  directory: \"./config\",\n  schema: configSchema,\n  createStack: (scope, config) => new MyAppStack(scope, \"MyApp\", config),\n});\n```\n\n## CLI Commands\n\n### catnip — Cloud Toolkit by the CAT Department\n\n`catnip` provides operational helpers for CloudFormation, ECS, and Cognito.\n\nGlobal options (apply to all commands):\n- `--region <region>` — AWS region (defaults to `AWS_DEFAULT_REGION` / `AWS_REGION`)\n- `--profile <profile>` — AWS named profile\n\n#### stack-diagnose\n\nDiagnose failed CloudFormation deployments and show ECS failure context.\n\nUsage:\n\n```bash\ncatnip stack-diagnose\ncatnip stack-diagnose --stack-name my-stack\ncatnip stack-diagnose --stage prod\ncatnip stack-diagnose --stack-name my-stack --tail 200 --tasks 10\n```\n\nOptions:\n- `--stack-name <name>` — stack to diagnose (optional; auto-detects last failed stack if omitted)\n- `--stage <name>` — stage filter for auto-detection (ignored if `--stack-name` is provided)\n- `--tail <n>` — Number of log lines to show per container (default: 100)\n- `--tasks <n>` — Number of recent stopped tasks to inspect (default: 5)\n\n#### ecs-logs\n\nStream live logs from running ECS services in a CloudFormation stack.\n\nUsage:\n\n```bash\ncatnip ecs-logs --stack-name my-stack\ncatnip ecs-logs --stack-name my-stack --follow\ncatnip ecs-logs --stack-name my-stack --service api --tail 50\ncatnip ecs-logs --stack-name my-stack --output raw\ncatnip ecs-logs --stack-name my-stack --output pretty\n```\n\nOptions:\n- `--stack-name <name>` — CloudFormation stack name (required)\n- `--tail <n>` — Lines of history to show per container (default: 100)\n- `-f, --follow` — Keep polling for new log events\n- `--service <name>` — Filter services by name\n- `-o, --output <mode>` — Output mode: `text`, `raw`, or `pretty` (default: text)\n\n#### oidc-token\n\nFetch a Cognito token using CloudFormation exports from a stack.\n\nUsage:\n\n```bash\ncatnip oidc-token --stack-name my-stack\ncatnip oidc-token --stack-name my-stack --output json\n```\n\nOptions:\n- `--stack-name <name>` — stack that exported Cognito resources (required)\n- `--output <token|json>` — print token only, or full response JSON (default: `token`)\n  - `token` output is the `access_token`\n\n## Documentation\n\n- [API Reference](./API.md)\n\n## License\n\nApache-2.0 © BTC Embedded Systems AG\n"
   },
   "repository": {
     "type": "git",
@@ -19883,6 +19883,6 @@
       "symbolId": "src/platform/VpcV2:VpcV2Props"
     }
   },
-  "version": "0.22.14",
-  "fingerprint": "U8Tf9Fotr6vHDrm2zRyhR1fc7JPRXSPw+mJRL6JSFRI="
+  "version": "0.22.15",
+  "fingerprint": "axwLf8KDZSEYVbCwcQlEDJQHzf288NA3QXr3+g15BM8="
 }

package/CHANGELOG.md

@@ -1,4 +1,11 @@
 
+## [0.22.14](https://github.com/btc-embedded/cdk-extensions/compare/v0.22.13...v0.22.14) (2026-02-26)
+
+
+### Bug Fixes
+
+* **cli:** improve stack-diagnose fallback log retrieval ([73616eb](https://github.com/btc-embedded/cdk-extensions/commit/73616eb32e84586ed916f0d5075f785292befe59))
+
 ## [0.22.13](https://github.com/btc-embedded/cdk-extensions/compare/v0.22.12...v0.22.13) (2026-02-26)
 
 

package/README.md

@@ -77,93 +77,67 @@ createApplicationApp({
 
 ### catnip — Cloud Toolkit by the CAT Department
 
-The `catnip` CLI tool provides commands for cloud infrastructure diagnostics and management.
+`catnip` provides operational helpers for CloudFormation, ECS, and Cognito.
+
+Global options (apply to all commands):
+- `--region <region>` — AWS region (defaults to `AWS_DEFAULT_REGION` / `AWS_REGION`)
+- `--profile <profile>` — AWS named profile
 
 #### stack-diagnose
 
-Diagnose CloudFormation stack deployment failures.
+Diagnose failed CloudFormation deployments and show ECS failure context.
 
-**Usage:**
+Usage:
 
 ```bash
-# Auto-detect and diagnose the last failed stack
 catnip stack-diagnose
-
-# Diagnose a specific stack
 catnip stack-diagnose --stack-name my-stack
-
-# Customize log output and task inspection
+catnip stack-diagnose --stage prod
 catnip stack-diagnose --stack-name my-stack --tail 200 --tasks 10
 ```
 
-**Description:**
-
-The `stack-diagnose` command provides comprehensive diagnostics for failed CloudFormation stacks. If no stack name is provided, it automatically detects and diagnoses the last failed stack in your AWS account. The command displays:
-
-- **Stack Status**: Current CloudFormation stack status and reason for failure
-- **CloudFormation Events**: Recent stack events showing what failed during deployment
-- **ECS Diagnostics** (if applicable): If the stack contains ECS services, additional diagnostics are performed including:
-  - Service event history
-  - Recent stopped task logs
-  - Container output for troubleshooting
-
-**Options:**
-
-- `--stack-name <name>` — CloudFormation stack name (optional; auto-detects last failed stack if omitted)
-- `--stage <name>` — Filter stacks by stage name (e.g., 'prod', 'dev') when auto-detecting; only used if --stack-name is not provided
+Options:
+- `--stack-name <name>` — stack to diagnose (optional; auto-detects last failed stack if omitted)
+- `--stage <name>` — stage filter for auto-detection (ignored if `--stack-name` is provided)
 - `--tail <n>` — Number of log lines to show per container (default: 100)
 - `--tasks <n>` — Number of recent stopped tasks to inspect (default: 5)
-- `--region <region>` — AWS region (uses AWS_DEFAULT_REGION / AWS_REGION environment variable if not specified)
-- `--profile <profile>` — AWS named profile for local development
-
-**Examples:**
-
-```bash
-# Quick diagnosis of last failed stack
-catnip stack-diagnose
-
-# Auto-detect failed stack for a specific stage (useful when multiple stages in same account)
-catnip stack-diagnose --stage prod
-
-# Diagnose specific stack with extended logging
-catnip stack-diagnose --stack-name prod-api-stack --tail 500 --tasks 10
-
-# Use specific AWS profile and region
-catnip stack-diagnose --profile my-profile --region eu-central-1
-```
 
 #### ecs-logs
 
 Stream live logs from running ECS services in a CloudFormation stack.
 
-**Usage:**
+Usage:
 
 ```bash
-# Stream logs from all ECS services in a stack
-npx catnip ecs-logs --stack-name my-stack
-
-# Follow logs in real-time
-npx catnip ecs-logs --stack-name my-stack --follow
-
-# Filter by service name and show last 50 lines
-npx catnip ecs-logs --stack-name my-stack --tail 50 --service api
-
-# Raw JSON output (for piping to jq or pino-pretty)
-npx catnip ecs-logs --stack-name my-stack --output raw
-
-# Pretty-printed JSON with colors
-npx catnip ecs-logs --stack-name my-stack --output pretty
+catnip ecs-logs --stack-name my-stack
+catnip ecs-logs --stack-name my-stack --follow
+catnip ecs-logs --stack-name my-stack --service api --tail 50
+catnip ecs-logs --stack-name my-stack --output raw
+catnip ecs-logs --stack-name my-stack --output pretty
 ```
 
-**Options:**
-
+Options:
 - `--stack-name <name>` — CloudFormation stack name (required)
 - `--tail <n>` — Lines of history to show per container (default: 100)
 - `-f, --follow` — Keep polling for new log events
 - `--service <name>` — Filter services by name
 - `-o, --output <mode>` — Output mode: `text`, `raw`, or `pretty` (default: text)
-- `--region <region>` — AWS region
-- `--profile <profile>` — AWS profile
+
+#### oidc-token
+
+Fetch a Cognito token using CloudFormation exports from a stack.
+
+Usage:
+
+```bash
+catnip oidc-token --stack-name my-stack
+catnip oidc-token --stack-name my-stack --output json
+```
+
+Options:
+- `--stack-name <name>` — stack that exported Cognito resources (required)
+- `--output <token|json>` — print token only, or full response JSON (default: `token`)
+  - `token` output is the `access_token`
 
 ## Documentation