alula-ruby 0.69.3 → 0.69.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fc02de3375ff5f9750d30b9610b51424840e0b449f0f3274e45e96cb12fed832
-  data.tar.gz: 45c91282440ebbc5f22765200688a994b58eac03ecc3b5b49bf89a8bce5db375
+  metadata.gz: 437c958452dd1cf0061a5b8534ce846bc52414e2e0128c68a610e303bac9a9dc
+  data.tar.gz: 86957f2ae1686b84d4b9626627a54db887de8a765eb6cec22b7d4af6dfabe5ca
 SHA512:
-  metadata.gz: eba2475e4987a5ff0ba1d0870022ca24c4b437932034cf866918e2cb8ec92d7d060b05844bb51e6ba8250dcf1f2c0c592cf0664e10617be2f39fbb2cb931f9b5
-  data.tar.gz: 428146bea507070b3fc1eb502b8a2865701e96b78fe9add79d8d70e1f51bbfca4a2627445aebff20e09a62b22e6eb61754c0be7811ce5605c8a15f8c7e13a725
+  metadata.gz: 8a528999fda192104ce96e7a70eb51f774f2d0e627e3b42e1327782664fd3006ce25693d772c7b52983217e131ef0c2d498367d82b4f1f4bc9c2245bb56992ad
+  data.tar.gz: e9d24baecbd89acf37bdfffc576fc6fd3104c224fae93be247b12080943c0c6f51a1159be9487208b8ceaaf20bced294ee64d7d23b4c9c579179f79b4c745ebf

data/README.md

@@ -2,6 +2,10 @@
 
 This is the official Alula ruby API client.
 
+```
+Refer to last two sections if you're making changes in alula-ruby to be used as gem file in AC.
+```
+
 ## Installation
 
 This gem is private, and can be installed via bundler using a Git fetch strategy:
@@ -415,18 +419,43 @@ Alula Ruby runs its unit & integratin tests against a copy of the API running in
 Occasionally under heavy use the dockerized API may lose or drop its databases, resulting in the test suite erroring completly and very quickly. To fix this simply restart the API with `docker-compose -f alula-docker-compose.yml down && docker-compose -f alula-docker-compose.yml up -d`
 
 
+## Importing GEM in AC Docker
+
+Most of the times, the work we do in alula ruby includes just updating the model/procedures and push the changes, without having to worry about the configuration mentioned above. When we make changes to alula ruby locally we need to test if the gem file works.
+For that we need to point to the local alula ruby gem we're working on from AC.
+
+This is straight forward if you're not using docker: provide the path of gem file in Gemfile in AC. But if you're using docker then you'll have to load the volume in the docker first and then update the
+gemfile to that specific volume.
+
+- In docker-compose.yml of your AC update the alulaconnect/volumes as:
+
+  `-  ~/Documents/alula-project/alula-ruby:/app/alula-ruby`
+
+  In this step, you are basically pointing to the file location of your alula-ruby and loading it in the docker volume as 'app/alula-ruby'. Make sure that you got the path of your alula ruby correct.
+
+- Second step is to import the gem file from the loaded volume. Update your Gemfile in AC as:
+
+  `gem 'alula-ruby',  path: "/app/alula-ruby"`
+
+  Make sure that you comment out the existing import where we're fetching gem from the remote server.
+
+Once this is done, you're ready to test your local alula-ruby gem on the alula connect side.
+
 ## Releasing
 
 In your PR:
 
 - Update VERSION.md with a new version number and a change list
 - Update `lib/alula/version.rb` with the new version number
-- Execute `bundle install` to update the lockfile
 - Commit these changes & include them in your PR.
 
 After merging your PR:
 
-- Check out `master` and pull to get the latest
+- Check out `main` and pull to get the latest.
+
+Update the following in AC side, the commits are to be made from AC for the files mentioned:
+
+- Once merge is done and build is successful update the gem 'alula-ruby' in alula connect Gemfile to the latest version you updated. Also run `bundle install` to update Gemfile.lock file. Commit both files. Failing to do so will break the build process of alula connect.
 <!-- 
 - Run `bundle exec rake release`.
   _A tag will be pushed to Github and then the UI will ask you input to push to a nonexistant URL. Just spam the enter key and let it error out. It's the tag on github that we care about._ [[ github action takes care of this ]] -->

data/VERSION.md

@@ -104,3 +104,4 @@
 | v0.69.1 | 2022-12-16  | Alias model added |
 | v0.69.2 | 2023-01-05  | Whitelisted camera vendors dealer attribute |
 | v0.69.3 | 2023-01-13  | Password reset RPC |
+| v0.69.4 | 2023-01-26  | User video Profile and readme update |

data/lib/alula/resources/user.rb

@@ -17,7 +17,7 @@ module Alula
     relationship :address, type: 'users-addresses', cardinality: 'To-one'
     relationship :pushtokens, type: 'users-pushtokens', cardinality: 'To-many'
     relationship :preferences, type: 'users-preferences', cardinality: 'To-one'
-    relationship :videoprofiles, type: 'users-videoprofiles', cardinality: 'To-many'
+    relationship :users_video_profile, type: 'users-videoprofiles', cardinality: 'To-many'
 
     # Resource Fields
     # Not all params are used at the moment. See Alula::ResourceAttributes for details

data/lib/alula/resources/user_videoprofile.rb

@@ -34,5 +34,12 @@ module Alula
           filterable: false,
           creatable_by: [:system, :station, :dealer, :technician],
           patchable_by: [:system, :station, :dealer, :technician]
+
+    field :vendors,
+          type: :array,
+          sortable: false,
+          filterable: false,
+          creatable_by: [:system, :station, :dealer, :technician],
+          patchable_by: [:system, :station, :dealer, :technician]
   end
 end

data/lib/alula/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Alula
-  VERSION = '0.69.3'
+  VERSION = '0.69.4'
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: alula-ruby
 version: !ruby/object:Gem::Version
-  version: 0.69.3
+  version: 0.69.4
 platform: ruby
 authors:
 - Titus Johnson
 autorequire: 
 bindir: exe
 cert_chain: []
-date: 2023-01-17 00:00:00.000000000 Z
+date: 2023-01-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: httparty