souls 1.8.17 → 1.9.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a08f3642096849fe5c48e6db57dbee722573b0b222829043dbb43f94c3720696
-  data.tar.gz: cda60b0e448c4567904a9e4d4ad1a0b148cb105f7cc2622fcf0b9a190b6f3d48
+  metadata.gz: b722ae9b809027ed3f277c78d1f317f2a7895f3dd5dad7e34d399bd6d50fd204
+  data.tar.gz: fe87897572e0abf64687f4401571c60c9ac2fe9ecb434862650392b61170492e
 SHA512:
-  metadata.gz: 3c7f93df1bbaca884fd667294eea99e635f525c8394e734c1a9af7018e71a6fd23f66ef75958aeee2d2bee932541470d29bb2bee07db150094894bf09af2900b
-  data.tar.gz: 3e06e81a5e6197dc728bfa0b81a637ab76c0c7733ae6e1669d7559712cfd88b0656ce01367e55434a882f59ea972626c6c6895dc482edbbc648b182864b0b855
+  metadata.gz: 01ce609f82f57560a167a62dbe4329b7a46db5a234a0dce2e4368fbf117a2a5e88e3d6cae3423a246f274de36e28adb9bb7497cda671bd7eb1296b1860aca54f
+  data.tar.gz: 9b45d88872e0d3ae5995511376d9fe6327d15f6c5a01807312a467a4e2c19c24bbfe6458d6cdb8b76528c6aa62be2d6a72d001964ba3b79685883d461b2bbad4

data/CODE_OF_CONDUCT.md

@@ -1,74 +1,133 @@
+
 # Contributor Covenant Code of Conduct
 
 ## Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
 
 ## Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to a positive environment for our
+community include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
 
-Examples of unacceptable behavior by participants include:
+Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
 * Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
-## Our Responsibilities
+## Enforcement Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
 
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at fumitake.kawasaki@el-soul.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
 
-[homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

data/lib/souls/cli/create/index.rb

@@ -170,6 +170,9 @@ end
                   service_account_key: ${{ secrets.SOULS_GCP_SA_KEY }}
                   export_default_credentials: true
 
+              - name: Sync Tasks
+                run: cd apps/#{worker_name} && souls gcloud scheduler sync_schedules
+
               - name: Configure Docker
                 run: gcloud auth configure-docker --quiet
 
@@ -195,7 +198,7 @@ end
                       --set-env-vars="SOULS_DB_USER=${{ secrets.SOULS_DB_USER }}" \\
                       --set-env-vars="SOULS_DB_PW=${{ secrets.SOULS_DB_PW }}" \\
                       --set-env-vars="SOULS_DB_HOST=${{ secrets.SOULS_DB_HOST }}" \\
-                      --set-env-vars="SOULS_TZ=${{ secrets.SOULS_TZ }}" \\
+                      --set-env-vars="TZ=${{ secrets.TZ }}" \\
                       --set-env-vars="SOULS_SECRET_KEY_BASE=${{ secrets.SOULS_SECRET_KEY_BASE }}" \\
                       --set-env-vars="SOULS_PROJECT_ID=${{ secrets.SOULS_GCP_PROJECT_ID }}"
         TEXT
@@ -224,8 +227,6 @@ end
           end
         TEXT
       end
-    rescue StandardError => e
-      puts(e)
     end
 
     def souls_helper_rbs(worker_name: "mailer")
@@ -273,11 +274,12 @@ end
       version = Souls.get_latest_version_txt(service_name: "worker").join(".")
       file_name = "worker-v#{version}.tgz"
       url = "https://storage.googleapis.com/souls-bucket/boilerplates/workers/#{file_name}"
+      puts(url)
       system("curl -OL #{url}")
       system("tar -zxvf ./#{file_name}")
       system("mv ./worker apps/#{worker_name}")
       system("cp ./apps/api/config/database.yml ./apps/#{worker_name}/config/")
-      FileUtils.rm(file_name)
+      FileUtils.rm_f(file_name)
     end
 
     def souls_worker_credit(worker_name: "mailer")

data/lib/souls/cli/gcloud/iam/index.rb

@@ -91,7 +91,8 @@ module Souls
         "roles/iam.serviceAccountUser",
         "roles/run.admin",
         "roles/storage.admin",
-        "roles/storage.objectAdmin"
+        "roles/storage.objectAdmin",
+        "roles/cloudscheduler.admin"
       ]
       roles.each do |role|
         add_service_account_role(role: role)

data/lib/souls/cli/gcloud/index.rb

@@ -3,6 +3,7 @@ require_relative "./pubsub/index"
 require_relative "./run/index"
 require_relative "./sql/index"
 require_relative "./compute/index"
+require_relative "./scheduler/index"
 require_relative "../cli_exception"
 
 module Souls
@@ -22,13 +23,16 @@ module Souls
     desc "run [COMMAND]", "souls gcloud run Commands"
     subcommand "cloud_run", CloudRun
 
+    desc "scheduler [COMMAND]", "souls gcloud schedluer Commands"
+    subcommand "scheduler", CloudScheduler
+
     map run: "cloud_run"
 
     desc "auth_login", "gcloud config set and gcloud auth login"
     def auth_login
       project_id = Souls.configuration.project_id
       system("gcloud projects describe #{project_id}", out: File::NULL) or raise(Souls::GcloudException)
-      system("gcloud config set project #{project_id}")
+      system("gcloud config set project #{project_id} >/dev/null 2>&1")
       system("gcloud auth login")
     end
 
@@ -36,7 +40,7 @@ module Souls
     def config_set
       project_id = Souls.configuration.project_id
       system("gcloud projects describe #{project_id}", out: File::NULL) or raise(Souls::GcloudException)
-      system("gcloud config set project #{project_id}")
+      system("gcloud config set project #{project_id} >/dev/null 2>&1")
     end
 
     desc "enable_permissions", "Enable Google Cloud APIs for SOULs Framework"
@@ -50,6 +54,7 @@ module Souls
       system("gcloud services enable containerregistry.googleapis.com")
       system("gcloud services enable run.googleapis.com")
       system("gcloud services enable vpcaccess.googleapis.com")
+      system("gcloud services enable cloudscheduler.googleapis.com")
     end
   end
 end

data/lib/souls/cli/gcloud/run/index.rb

@@ -1,15 +1,5 @@
 module Souls
   class CloudRun < Thor
-    desc "awake", "Set Ping Every 15min by Google Cloud Scheduler"
-    method_option :url, default: "https://souls.souls.nl", aliases: "--url", desc: "Set URL"
-    def awake
-      app_name = Souls.configuration.app
-      system(
-        "gcloud scheduler jobs create http #{app_name}-awake
-            --schedule '0,10,20,30,40,50 * * * *' --uri #{url} --http-method GET"
-      )
-    end
-
     desc "list", "Show Google Cloud Run List"
     def list
       system("gcloud run services list --platform managed")

data/lib/souls/cli/gcloud/scheduler/index.rb

@@ -0,0 +1,28 @@
+module Souls
+  class CloudScheduler < Thor
+    desc "awake", "Set Ping Every 15min by Google Cloud Scheduler"
+    method_option :url, default: "https://souls.souls.nl", aliases: "--url", desc: "Set URL"
+    def awake
+      app_name = Souls.configuration.app
+      system(
+        "gcloud scheduler jobs create http #{app_name}-awake
+            --schedule '0,10,20,30,40,50 * * * *' --uri #{options[:url]} --http-method GET"
+      )
+    end
+
+    desc "sync_schedules", "Collect schedules from queries and sync with GCloud"
+    def sync_schedules
+      require("./app")
+      Souls::Gcloud.new.config_set
+      Queries::BaseQuery.all_schedules.each do |k, v|
+        worker_name = FileUtils.pwd.split("/").last
+        job_name = "#{worker_name}_#{k.to_s.underscore}"
+        system("gcloud scheduler jobs delete #{job_name} -q >/dev/null 2>&1")
+        system(
+          <<~COMMAND)
+            gcloud scheduler jobs create pubsub #{job_name} --quiet --schedule="#{v}" --topic="#{k}" --attributes="" --message-body="#{k}"
+          COMMAND
+      end
+    end
+  end
+end

data/lib/souls/version.rb

@@ -1,4 +1,4 @@
 module Souls
-  VERSION = "1.8.17".freeze
+  VERSION = "1.9.3".freeze
   public_constant :VERSION
 end

data/lib/souls/versions/.souls_api_version

@@ -1 +1 @@
-1.8.17
+1.9.3

data/lib/souls/versions/.souls_worker_version

@@ -1 +1 @@
-1.8.17
+1.9.3

metadata

@@ -1,16 +1,16 @@
 --- !ruby/object:Gem::Specification
 name: souls
 version: !ruby/object:Gem::Version
-  version: 1.8.17
+  version: 1.9.3
 platform: ruby
 authors:
 - POPPIN-FUMI
 - KishiTheMechanic
 - James Neve
-autorequire:
+autorequire: 
 bindir: exe
 cert_chain: []
-date: 2021-11-23 00:00:00.000000000 Z
+date: 2021-11-24 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: activesupport
@@ -168,6 +168,7 @@ files:
 - lib/souls/cli/gcloud/pubsub/subscriptions.rb
 - lib/souls/cli/gcloud/pubsub/topics.rb
 - lib/souls/cli/gcloud/run/index.rb
+- lib/souls/cli/gcloud/scheduler/index.rb
 - lib/souls/cli/gcloud/sql/index.rb
 - lib/souls/cli/generate/application.rb
 - lib/souls/cli/generate/connection.rb
@@ -226,7 +227,7 @@ licenses:
 - Apache-2.0
 metadata:
   rubygems_mfa_required: 'true'
-post_install_message:
+post_install_message: 
 rdoc_options: []
 require_paths:
 - lib
@@ -242,7 +243,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubygems_version: 3.2.22
-signing_key:
+signing_key: 
 specification_version: 4
 summary: Build Serverless Apps faster like Rails. Powered by Ruby GraphQL, RBS/Steep,
   Active Record, RSpec, RuboCop, and Google Cloud.