@btc-embedded/cdk-extensions 0.22.9 → 0.22.11

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## 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\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- `--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# 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"
   },
   "repository": {
     "type": "git",
@@ -19883,6 +19883,6 @@
       "symbolId": "src/platform/VpcV2:VpcV2Props"
     }
   },
-  "version": "0.22.9",
-  "fingerprint": "8kkFTwikvrcBXCvG9u55cDgpuJmUgRpdHabxUvsrwsw="
+  "version": "0.22.11",
+  "fingerprint": "tFOP05AizrkdYOh25E8nhxF4BCsuHDrs+B731DuvmNQ="
 }

package/CHANGELOG.md

@@ -1,4 +1,28 @@
 
+## [0.22.10](https://github.com/btc-embedded/cdk-extensions/compare/v0.22.9...v0.22.10) (2026-02-25)
+
+
+### Features
+
+* **cli:** add CloudFormation stack status utilities ([dfff3ed](https://github.com/btc-embedded/cdk-extensions/commit/dfff3edfa6cbf0f15a531e320ab8a43f80dcd4e3))
+* **cli:** add stack-diagnose command ([7d60af8](https://github.com/btc-embedded/cdk-extensions/commit/7d60af8979affeeb8ba6e087860228a640c08de1))
+* **cli:** register stack-diagnose command ([a82d60a](https://github.com/btc-embedded/cdk-extensions/commit/a82d60a78a6ae5737a6bd149d9306ce0ac13cc88))
+
+## [0.22.9](https://github.com/btc-embedded/cdk-extensions/compare/v0.22.8...v0.22.9) (2026-02-20)
+
+
+### Features
+
+* add catnip CLI tool with ecs-diagnose and oidc-token commands ([242e3e3](https://github.com/btc-embedded/cdk-extensions/commit/242e3e3bc70fef200aafa81f0e43a41a30c65ee0))
+
+
+### Bug Fixes
+
+* enforce no-any and no-type-assertion ESLint rules ([dc60f7d](https://github.com/btc-embedded/cdk-extensions/commit/dc60f7d9fc92c8bd56d4a597442fdae02a7bcd6e))
+* handle old ECS ARN format and validate parseInt inputs ([fd4adce](https://github.com/btc-embedded/cdk-extensions/commit/fd4adce2a6297291388ddd8b52a7873da120acef))
+* resolve @smithy/types version conflict in DynamoDB mock tests ([5cc979d](https://github.com/btc-embedded/cdk-extensions/commit/5cc979d62db4e270e0199abe8a57efeaa43ade21))
+* resolve Cognito token endpoint from full FQDN or domain prefix ([4b9e04e](https://github.com/btc-embedded/cdk-extensions/commit/4b9e04e14f82af902512d61ca486978e2e4f690f))
+
 ## [0.22.8](https://github.com/btc-embedded/cdk-extensions/compare/v0.22.7...v0.22.8) (2026-02-12)
 
 

package/README.md

@@ -73,6 +73,94 @@ createApplicationApp({
 });
 ```
 
+## CLI Commands
+
+### catnip — Cloud Toolkit by the CAT Department
+
+The `catnip` CLI tool provides commands for cloud infrastructure diagnostics and management.
+
+#### stack-diagnose
+
+Diagnose CloudFormation stack deployment failures.
+
+**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 --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)
+- `--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
+
+# 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:**
+
+```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
+```
+
+**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
+
 ## Documentation
 
 - [API Reference](./API.md)