koppler 0.0.8 → 0.0.9

package/dist/page/index.html

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1" />
     <title>Koppler</title>
     <script src="./theme.js"></script>
-    <script type="module" crossorigin src="./assets/index-cGqfl7Ue.js"></script>
+    <script type="module" crossorigin src="./assets/index-Bi0_sPx0.js"></script>
     <link rel="stylesheet" crossorigin href="./assets/index-e6-Jk1nK.css">
   </head>
   <body>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "koppler",
-  "version": "0.0.8",
+  "version": "0.0.9",
   "description": "Run the part of your stack you need locally, wired together, while the rest keeps calling a deployed environment.",
   "license": "MIT",
   "author": "Ivan Yanowsky",

package/skills/koppler-run/VERSION

@@ -1 +1 @@
-0.0.8
+0.0.9

package/skills/koppler-run/references/research.md

@@ -42,7 +42,7 @@ Queues, topics and event buses go under `queues`, with `publishes` / `reads` on
 ## Trace what feeds a queue
 
 A queue an app reads is often the end of a chain: a Kafka topic piped onto an event bus, whose rule forwards to another account's bus, which a rule hands to a Lambda.
-`koppler discover --deployed` drafts what it can read from the Terraform; trace the rest by hand, in every clone, and record each link with `koppler stack set queues.<id>.feeds.<other> '{"via":"pipe"}'`:
+`koppler discover --deployed` drafts what it can read from the Terraform, and `koppler discover --deployed --aws` checks it against what AWS runs (read-only, the apps' own profiles): `FOUND` lines are links the stack misses. Trace the rest by hand, in every clone, and record each link with `koppler stack set queues.<id>.feeds.<other> '{"via":"pipe"}'`:
 - **Kafka topics read:** `aws_pipes_pipe` and `awscc_pipes_pipe` with `self_managed_kafka_parameters` or `managed_streaming_kafka_parameters`; `topic_name`, often `each.key` over a list variable whose values are in the `.tfvars` (a commented-out item is not read). Also Lambda event source mappings on an MSK or Kafka source.
 - **Kafka topics written:** app settings such as `KafkaSettings/Topic`, `Kafka__Topic` and `BootstrapServers` in the Terraform locals and `appsettings*.json`; the app `publishes` that topic.
 - **Event buses:** `aws_cloudwatch_event_bus`; its rules (`aws_cloudwatch_event_rule` with `event_bus_name`) and their targets (`aws_cloudwatch_event_target`): a queue, a Lambda, an API destination, or another account's bus by its ARN (`event-bus/<name>`, often in a map per environment in the locals).

package/skills/koppler-run/references/stack.md

@@ -166,7 +166,9 @@ Tests, docs, lock files and migration tools are not searched.
 - the names of its settings, and which of them hold or point to a secret;
 - Secrets Manager secret names and Parameter Store paths;
 - calls: a setting whose address belongs to another app;
-- queues, topics and event buses, and what feeds what (`queueSuggestions`): SQS queues and SNS topics, EventBridge buses (`aws_cloudwatch_event_bus`), Kafka topics a pipe reads (`topic_name` of an `aws_pipes_pipe` or `awscc_pipes_pipe`, one per topic of a list), pipes (source to target), rules with their targets (a bus to a queue, a Lambda, or another account's bus by its ARN), and SNS subscriptions (`aws_sns_topic_subscription`). A queue read through a pipe or rule to a Lambda or an API destination is drafted as `reads` with `via`, such as `"rule to Lambda"`. Feeds of queues the stack already has are under `queueSuggestions.feeds`.
+- queues, topics and event buses, and what feeds what (`queueSuggestions`): SQS queues and SNS topics, EventBridge buses (`aws_cloudwatch_event_bus`), Kafka topics a pipe reads (`topic_name` of an `aws_pipes_pipe` or `awscc_pipes_pipe`, one per topic of a list), pipes (source to target), rules with their targets (a bus to a queue, a Lambda, or another account's bus by its ARN), and SNS subscriptions (`aws_sns_topic_subscription`). A queue read through a pipe or rule to a Lambda or an API destination is drafted as `reads` with `via`, such as `"rule to Lambda"`. Feeds of queues the stack already has are under `queueSuggestions.feeds`. Topic names in a map (`for_each = var.kafka.topics`, `each.value`), in a `.tfvars.json`, or in the variables of the folder above a module are read too.
+
+`koppler discover --deployed --aws [--env <env>]` then checks what AWS runs between the queues, with each app's AWS profile for that environment (its `-view` twin when the AWS config has one): it only lists and describes EventBridge Pipes and Lambda event source mappings, never a value or a message. Each line is `OK`, `FOUND` (in AWS, not in the stack) or `MISSING` (in the stack, not in AWS); a profile that is not signed in is named with its `aws sso login` command.
 
 It reads out names and plain addresses only (a host, or an http(s) URL with no credentials or query); every other value stays in the repo.
 Environments come from variable files named after them (`deployment-dev.tfvars`) or, without those, from trying each stack environment and alias as the Terraform workspace.