foobara-aws 0.2.0 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4d08fb1f5a14798c744facb5a4f0a3986b544482f486b3962b90d8248b20bfab
-  data.tar.gz: 568943fcb7e647eb2fd620b0430076a173065bc8760ce8c0d6ec7cc7f89a8017
+  metadata.gz: 16a858ce4e2944711259dacbf844fd258a1715018aaa7df98364e45739ec33de
+  data.tar.gz: 995b9e3af507e6cb53e3fd581945d27b9251f9559f0151c9151e5fa5bb277191
 SHA512:
-  metadata.gz: aae339846f621a18ccb328143d5543aa6b3cc42ab8e0f8429cbb8c2f69c156bf7000286fa6e3fa488a838cec557244581de972229320f38c5ea6d9cd28123f00
-  data.tar.gz: d02982c0c6f67749b548f411f246f614778f59af62043bd529f4227006ed83b06c9302af32271e388b60a90866be94104947859cc4a066f442a7dc28960745b5
+  metadata.gz: a328cae1d9959faa1efc89dc399f007005673493704ae20dbe9e02904b85949f7eb76debefeff09830f2a367315efac9bde77981c660690299aced88f5871464
+  data.tar.gz: a0cb8f25daa37b5ea097d5bf13e145c0a7df3a27b2d6faa801e426dafb3f8f00def81a55093d7c95818cd2caf32b2d7bbe7c6f3864248993b099f749d1218d52

data/CHANGELOG.md

@@ -1,5 +1,15 @@
 ## [Unreleased]
 
+## [0.3.0] - 2026-08-04
+
+- `Foobara::AWS.plan_from_connector(connector)` — build a plan by inspecting a live connector instead of a
+  manifest. No HTTP, no running server, and no snapshot on disk to go stale.
+- It takes a CONNECTOR rather than a set of command classes, because `requires_authentication` is decided at
+  `connect` time and lives on the transformed command. The command classes alone cannot say which commands are
+  public, which is the one thing a deployment most needs to know.
+- It adapts each command into the shape `plan` already reads, so there is a single derivation and the two routes
+  cannot drift — asserted by a spec comparing the plans they produce.
+
 ## [0.2.0] - 2026-08-04
 
 - `Foobara::AWS::Check` — checks a DEPLOYED API against the plan it was deployed from. It asserts the few things

data/README.md

@@ -15,6 +15,22 @@ service = Foobara::AWS::CDK::Service.new(self, "Api", plan: plan, code_root: "bu
 posts_table.grant_read_write_data(service.function("posts"))
 ```
 
+## Where a plan comes from
+
+```ruby
+Foobara::AWS.plan(manifest)                  # a manifest, however you obtained it
+Foobara::AWS.plan_from_connector(connector)  # a live connector, no server needed
+Foobara::AWS::Plan.load(JSON.parse(json))    # one that has been through JSON
+```
+
+`plan_from_connector` is usually what a build step wants: it reads the objects
+directly, so there is no server to start and no snapshot to go stale. It takes a
+**connector**, not a set of command classes — `requires_authentication` is
+decided at `connect` time and lives on the transformed command, so the classes
+alone cannot say which commands are public.
+
+All three produce the same `Plan`, and a spec asserts the first two agree.
+
 ## Two halves, on purpose
 
 ```ruby

data/lib/foobara/aws/plan.rb

@@ -85,6 +85,28 @@ module Foobara
         Plan.new(mount: mount, granularity: granularity, units: units.sort_by(&:name))
       end
 
+      # Build a {Plan} by inspecting a live connector instead of a manifest.
+      #
+      # The same information by a shorter route: no HTTP, no running server, and
+      # no snapshot on disk to go stale. It needs the application loaded, so it
+      # belongs in a build step rather than in a CDK app — which is the whole
+      # reason a {Plan} can also travel as JSON.
+      #
+      # A CONNECTOR, not a set of command classes. `requires_authentication` is
+      # decided at `connect` time and lives on the transformed command, so the
+      # command classes alone cannot say which commands are public — which is the
+      # one thing a deployment most needs to know.
+      #
+      # It adapts each command into the shape {plan} already reads, so there is
+      # one implementation and the two routes cannot drift.
+      def plan_from_connector(connector, **)
+        commands = connector.command_registry.all_transformed_command_classes.to_h do |transformed|
+          [transformed.command_class.full_command_name, describe_command(transformed)]
+        end
+
+        plan({ "command" => commands }, **)
+      end
+
       # Foobara's own commands — its auth domain and anything else it registers —
       # are infrastructure, not the application, and deploying them is never what
       # anyone means. Matched on the command's full name, which is where that
@@ -97,6 +119,35 @@ module Foobara
 
       private
 
+      # Manifest-shaped, so {plan} cannot tell the difference. Only the fields
+      # planning reads — a manifest carries much more, and none of the rest
+      # matters here.
+      def describe_command(transformed)
+        command_class = transformed.command_class
+
+        {
+          "domain" => domain_name(command_class),
+          "organization" => organization_name(command_class),
+          "scoped_full_path" => Array(command_class.scoped_full_path),
+          "requires_authentication" => transformed.requires_authentication,
+          "depends_on" => Array(command_class.depends_on).map(&:to_s),
+          # The AWSLambda DSL, when the command extends it.
+          "aws_lambda" => (command_class.aws_lambda_manifest if command_class.respond_to?(:aws_lambda_manifest))
+        }.compact
+      end
+
+      def domain_name(command_class)
+        command_class.domain.scoped_full_name
+      rescue StandardError
+        ""
+      end
+
+      def organization_name(command_class)
+        command_class.organization.scoped_full_name
+      rescue StandardError
+        ""
+      end
+
       def app_commands(manifest, exclude)
         manifest.fetch("command").reject do |name, _command|
           exclude.any? { |prefix| name.to_s.start_with?(prefix) }

data/lib/foobara/aws/version.rb

@@ -2,6 +2,6 @@
 
 module Foobara
   module AWS
-    VERSION = "0.2.0"
+    VERSION = "0.3.0"
   end
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: foobara-aws
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.3.0
 platform: ruby
 authors:
 - Omar Qureshi