putpaws 0.1.4 → 0.1.5

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d38b16d5a4fc24915b8bde117f9fda98d0fb6418989eebf98385e86ad724dd32
-  data.tar.gz: c3ee3c20989376d82da51e970aa23ab2995af32c39b0e37524c7fa915cf9a8f9
+  metadata.gz: 6b0c08e32fd66d0f401c637c162bb7d2e408beb0110e433fec09d2a5853e0372
+  data.tar.gz: faeacb4b1476fd8247f627e32640ddaaac55e906754bba8e0155adc35a624225
 SHA512:
-  metadata.gz: e2d00b74e706f5c9192a455bd7919845c4afeb06d2c3db9cd17c2030689cdc2858cc439efb6dd360cc8b9d4eb3fe6fceb6e9a62fb361de1ff0b8d30be4be10c2
-  data.tar.gz: 49fbf55b6659a02a563792d4ab406bbe1f583e84abf82eee10c5c52b12bbcb3da42d539fb1346dc10dd4a4a6ba70df427b8ddc5f1b5edf7c07e775c4b314fb72
+  metadata.gz: 8f43a0329c4b6705b72c235687f0ba9f3a038a1314c32dca0dcfb83f26f28326b0e7ae7d2d1cb13267674626ccd47786100b574b17fa95119606ebcf960b1193
+  data.tar.gz: 3488ea35bc10ce0ed4449ed0ca1ec97836f22535d246662f3d3f729779fc12d1e67b5a231cc28acc7fa9c816c369a59a37e6f5a9d5bda45c97fa9e9e70fc0291

data/README.md

@@ -55,6 +55,14 @@ or a new one is created for the service when left empty on `ready`.
 When the service step completes, the new service is reflected into
 `.putpaws/application.json` and `.putpaws/infra.json` (diff is shown and confirmed),
 so `ecs:attach`, `ecs:shell`, `ecs:run` and `log:*` work immediately.
+One entry is written per task definition of the preset, keyed by the task definition
+family `{service_name}-{suffix}` (Ex: `awesome-api-staging-app` / `awesome-api-staging-web`),
+each pointing at the `infra.target` of the same name. Only the entry of the preset's
+`service_task_definition` carries `service` (for `ecs:deploy` / `ecs:attach`); the others have
+`service: null` and are meant for one-off tasks (`ecs:run` / `ecs:shell` / scheduler),
+so `db:migrate` keeps running on the plain `app` task definition even when the service
+runs `web` (nginx + app). `infra.network` is written once as `{service_name}`.
+Existing keys are never deleted; remove stale ones by hand.
 Secrets are handled by reference only: task definitions point to existing
 SSM parameters (Ex: `/{service_name}/RAILS_MASTER_KEY`) and putpaws never touches the values.
 
@@ -225,19 +233,35 @@ gem 'putpaws'
 
 `.putpaws/application.json`
 
+Keys are free-form names you pass to the CLI. The ones written by `putpaws up` follow
+`{service_name}-{suffix}`: `-app` for one-off tasks (`service: null`), `-web` for the
+long-running service.
+
 ```
 {
-  "awesome-api-staging": {
+  "awesome-api-staging-app": {
     "region": "ap-northeast-1",
     "cluster": "cluster-staging",
     "service": null,
-    "task_name_prefix": "awesome-api",
-    "log_group_prefix": "/ecs/awesome/awesome-api-staging",
+    "task_name_prefix": "awesome-api-staging-app",
+    "log_group_prefix": "/ecs/awesome-api-staging",
+    "log_region": null,
+    "build_log_group_prefix": "/aws/codebuild/awesome-api-staging",
+    "build_project_name_prefix": "awesome-api-staging",
+    "network": "awesome-api-staging",
+    "target": "awesome-api-staging-app"
+  },
+  "awesome-api-staging-web": {
+    "region": "ap-northeast-1",
+    "cluster": "cluster-staging",
+    "service": "awesome-api-staging",
+    "task_name_prefix": "awesome-api-staging-web",
+    "log_group_prefix": "/ecs/awesome-api-staging",
     "log_region": null,
     "build_log_group_prefix": "/aws/codebuild/awesome-api-staging",
     "build_project_name_prefix": "awesome-api-staging",
-    "network": "awesome-private-staging",
-    "target": "awesome-staging"
+    "network": "awesome-api-staging",
+    "target": "awesome-api-staging-web"
   },
   "awesome-api-production": {
     "region": "ap-northeast-1",

data/lib/putpaws/provision/config_writer.rb

@@ -8,6 +8,15 @@ module Putpaws
     # Reflects provisioned resources into .putpaws/application.json and
     # .putpaws/infra.json. Only the keys of the target service are touched.
     # Shows a diff and asks for confirmation before writing.
+    #
+    # One application entry and one infra.target entry are written per task
+    # definition of the preset, keyed by the task definition family
+    # (`<service_name>-<suffix>`). The entry whose suffix is the preset's
+    # `service_task_definition` carries `service` so that ecs:deploy /
+    # ecs:attach address the long-running service; the others are for
+    # one-off tasks (ecs:run / ecs:shell / scheduler) and have `service: null`.
+    # infra.network is written once per service as it does not depend on the
+    # task definition.
     class ConfigWriter
       attr_reader :config, :state, :prompt, :io
       def initialize(config:, state:, prompt:, io: $stdout)
@@ -17,17 +26,18 @@ module Putpaws
         @io = io
       end
 
-      def application_entry
+      def application_entry(entry)
+        family = config.task_definition_family(entry[:suffix])
         {
           region: config.region,
           cluster: config.cluster_name,
-          service: config.service_name,
-          task_name_prefix: config.service_name,
+          service: service_entry?(entry) ? config.service_name : nil,
+          task_name_prefix: family,
           log_group_prefix: config.log_group,
           build_log_group_prefix: config.build_log_group,
           build_project_name_prefix: config.build_project_name,
           network: config.service_name,
-          target: config.service_name,
+          target: family,
         }
       end
 
@@ -39,25 +49,32 @@ module Putpaws
         }
       end
 
-      def target_entry
+      def target_entry(entry)
         {
           # Used by EventBridge Scheduler (scheduler:deploy).
           scheduler_role: config.roles[:scheduler_role_arn],
           cluster: state.resources[:cluster_arn],
           # Revision-less on purpose: always run the latest ACTIVE revision.
-          task_definition: config.service_task_definition_family,
-          container_name: config.service_container_name,
+          task_definition: config.task_definition_family(entry[:suffix]),
+          container_name: entry[:container_name] || 'app',
         }
       end
 
       def apply!
-        write_key(path('application.json'), [config.service_name.to_sym], application_entry)
         write_key(path('infra.json'), [:network, config.service_name.to_sym], network_entry)
-        write_key(path('infra.json'), [:target, config.service_name.to_sym], target_entry)
+        config.preset.task_definitions.each do |entry|
+          key = config.task_definition_family(entry[:suffix]).to_sym
+          write_key(path('application.json'), [key], application_entry(entry))
+          write_key(path('infra.json'), [:target, key], target_entry(entry))
+        end
       end
 
       private
 
+      def service_entry?(entry)
+        entry[:suffix] == config.preset.service_task_definition
+      end
+
       def path(basename)
         Pathname.new(config.path_prefix).join(basename)
       end

data/lib/putpaws/version.rb

@@ -1,3 +1,3 @@
 module Putpaws
-  VERSION = "0.1.4"
+  VERSION = "0.1.5"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: putpaws
 version: !ruby/object:Gem::Version
-  version: 0.1.4
+  version: 0.1.5
 platform: ruby
 authors:
 - metheglin