cyclone_lariat 1.0.0.rc1 → 1.0.0.rc2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 31cc88737fffda51fb2ba2f1ef8ea792adcd3d7d
-  data.tar.gz: 520aef70c935d03db0f7624a253f62ac6dddeaa7
+  metadata.gz: 57a9765a6c8e7239c17807d05e70399fccb2268d
+  data.tar.gz: e54780308582d37055e6d2444972e775f2ad9927
 SHA512:
-  metadata.gz: 062f76a7ef10d61bd94e624e4db72619ace3bf3d7ee05ab0ec7b32ecbca8895afda9dc060390aa0c157e1ae843a6e6bce99e815a965c6fde3e49655e9ceb3709
-  data.tar.gz: 91adda66efabdd82c60e2e1fb2f1a602a4b3c6f26300c5d3c82ac923466024fee705d5012d5c9cecae671081af0c91cbda52291ef3e896f4d182914f3f125ec1
+  metadata.gz: d54bdf09e3414a6d2c477a2bd465750e705ad961d6882d015452b48fef11b09fc24770b938a390a3dc7a91de3e0059a8908728eb22114c7bd330f1556fa7d187
+  data.tar.gz: 5bfe88a0227b3bd8016b6a9c46eb007def598f3da4ce872e12f72385de735fd5019c6b0f96fb3d3d0c6e117ea373a1216b74d2f48fbe78bdadcde2480405d954

data/CHANGELOG.md

@@ -4,6 +4,12 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [1.0.0.rc2]
+Changed
+- README.md file
+Added
+- require version file, fixed `bundle exec cyclone_lariat -v`
+
 ## [0.4.0]
 Changed
 - rename `topic` to `queue` for SQS operations, in fact it changed only in methods `publish_event`, `publish_command`
@@ -19,7 +25,7 @@ Added
 Added
 - Added aws_client_od options
 Changed:
-- Renamed all AWS options with prefix _aws 
+- Renamed all AWS options with prefix _aws
 
 ## [0.3.9] - 2022-10-05 Depricated
 Added

data/README.md

@@ -24,7 +24,7 @@ This gem work in few scenarios:
   And run in console:
   ```bash
   $ bundle install
-  $ cyclone_lariat install
+  $ bundle exec cyclone_lariat install
   ```
 </details>
 <details>
@@ -40,7 +40,7 @@ This gem work in few scenarios:
   And run in console:
   ```bash
   $ bundle install
-  $ cyclone_lariat install --adapter=active_record
+  $ bundle exec cyclone_lariat install --adapter=active_record
   ```
 </details>
 
@@ -344,7 +344,7 @@ class Publisher < CycloneLariat::Publisher
   def delete_user(mail)
     sns.publish command('delete_user', data: { mail: mail }), fifo: false
   end
-  
+
   def welcome_message(mail, text)
     sqs.publish command('welcome', data: {mail: mail, txt: text}), fifo: false
   end
@@ -408,13 +408,13 @@ CycloneLariat::Clients::Sns.new.publish_command(
 class Publisher < CycloneLariat::Publisher
   def register_user(first:, last:, mail:)
     sns.publish command(
-      'register_user', 
-      data: { 
-        mail: mail, 
+      'register_user',
+      data: {
+        mail: mail,
         name: {
-          first: first, 
+          first: first,
           last: last
-        } 
+        }
       }
     ), fifo: false
   end
@@ -482,16 +482,16 @@ end
 Will publish message on queue: `custom_topic_name`
 
 
-### FIFO and no FIFO 
+### FIFO and no FIFO
 The main idea you can read on [AWS Docs](https://aws.amazon.com/blogs/aws/introducing-amazon-sns-fifo-first-in-first-out-pub-sub-messaging/).
 
 FIFO message should consist two fields:
-- `group_id` - In each topic, the FIFO sequence is defined only within one group. 
+- `group_id` - In each topic, the FIFO sequence is defined only within one group.
  [AWS Docs](https://docs.aws.amazon.com/sns/latest/dg/fifo-message-grouping.html)
-- `deduplication_id` - Within the same group, a unique identifier must be defined for each message. 
+- `deduplication_id` - Within the same group, a unique identifier must be defined for each message.
  [AWS Docs](https://docs.aws.amazon.com/sns/latest/dg/fifo-message-dedup.html)
-  
- The unique identifier can definitely be the entire message. In this case, you 
+
+ The unique identifier can definitely be the entire message. In this case, you
  do not need to pass the deduplication_id parameter. But you must create a queue
    with the `content_based_deduplication` parameter in migration.
 
@@ -516,7 +516,7 @@ class Publisher < CycloneLariat::Publisher
           uuid: uuid,
           mail: mail
         },
-      }, 
+      },
       deduplication_id: mail,
       group_id: uuid),
     fifo: true
@@ -541,7 +541,7 @@ With **cyclone_lariat** you can use migrations that can create, delete, and subs
 Before using this function, you must complete the **cyclone_lariat** [configuration](#Configuration).
 
 ```bash
-$ cyclone_lariat generate migration user_created
+$ bundle exec cyclone_lariat generate migration user_created
 ```
 
 This command should create a migration file, let's edit it.
@@ -561,7 +561,7 @@ class UserCreatedQueue < CycloneLariat::Migration
   end
 end
 ```
-The `content_based_dedupplication` parameter can only be specified for FIFO resources. When true, the whole message is 
+The `content_based_dedupplication` parameter can only be specified for FIFO resources. When true, the whole message is
 used as the unique message identifier instead of the `deduplication_id` key.
 
 To apply migration use:
@@ -720,8 +720,8 @@ We recommend locate migration on:
 ## Console tasks
 
 ```bash
-$ cyclone_lariat install - install cyclone_lariat
-$ cyclone_lariat generate migration - generate new migration
+$ bundle exec cyclone_lariat install - install cyclone_lariat
+$ bundle exec cyclone_lariat generate migration - generate new migration
 
 $ rake cyclone_lariat:list:queues         # List all queues
 $ rake cyclone_lariat:list:subscriptions  # List all subscriptions

data/lib/cyclone_lariat/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module CycloneLariat
-  VERSION = '1.0.0.rc1'
+  VERSION = '1.0.0.rc2'
 end

data/lib/cyclone_lariat.rb

@@ -1,5 +1,6 @@
 # frozen_string_literal: true
 
+require 'cyclone_lariat/version'
 require 'cyclone_lariat/core'
 require 'cyclone_lariat/middleware'
 require 'cyclone_lariat/migration'

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: cyclone_lariat
 version: !ruby/object:Gem::Version
-  version: 1.0.0.rc1
+  version: 1.0.0.rc2
 platform: ruby
 authors:
 - Alexander Kudrin