alula-ruby 0.69.3 → 0.69.4
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +31 -2
- data/VERSION.md +1 -0
- data/lib/alula/resources/user.rb +1 -1
- data/lib/alula/resources/user_videoprofile.rb +7 -0
- data/lib/alula/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 437c958452dd1cf0061a5b8534ce846bc52414e2e0128c68a610e303bac9a9dc
|
4
|
+
data.tar.gz: 86957f2ae1686b84d4b9626627a54db887de8a765eb6cec22b7d4af6dfabe5ca
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 8a528999fda192104ce96e7a70eb51f774f2d0e627e3b42e1327782664fd3006ce25693d772c7b52983217e131ef0c2d498367d82b4f1f4bc9c2245bb56992ad
|
7
|
+
data.tar.gz: e9d24baecbd89acf37bdfffc576fc6fd3104c224fae93be247b12080943c0c6f51a1159be9487208b8ceaaf20bced294ee64d7d23b4c9c579179f79b4c745ebf
|
data/README.md
CHANGED
@@ -2,6 +2,10 @@
|
|
2
2
|
|
3
3
|
This is the official Alula ruby API client.
|
4
4
|
|
5
|
+
```
|
6
|
+
Refer to last two sections if you're making changes in alula-ruby to be used as gem file in AC.
|
7
|
+
```
|
8
|
+
|
5
9
|
## Installation
|
6
10
|
|
7
11
|
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
|
|
415
419
|
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`
|
416
420
|
|
417
421
|
|
422
|
+
## Importing GEM in AC Docker
|
423
|
+
|
424
|
+
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.
|
425
|
+
For that we need to point to the local alula ruby gem we're working on from AC.
|
426
|
+
|
427
|
+
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
|
428
|
+
gemfile to that specific volume.
|
429
|
+
|
430
|
+
- In docker-compose.yml of your AC update the alulaconnect/volumes as:
|
431
|
+
|
432
|
+
`- ~/Documents/alula-project/alula-ruby:/app/alula-ruby`
|
433
|
+
|
434
|
+
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.
|
435
|
+
|
436
|
+
- Second step is to import the gem file from the loaded volume. Update your Gemfile in AC as:
|
437
|
+
|
438
|
+
`gem 'alula-ruby', path: "/app/alula-ruby"`
|
439
|
+
|
440
|
+
Make sure that you comment out the existing import where we're fetching gem from the remote server.
|
441
|
+
|
442
|
+
Once this is done, you're ready to test your local alula-ruby gem on the alula connect side.
|
443
|
+
|
418
444
|
## Releasing
|
419
445
|
|
420
446
|
In your PR:
|
421
447
|
|
422
448
|
- Update VERSION.md with a new version number and a change list
|
423
449
|
- Update `lib/alula/version.rb` with the new version number
|
424
|
-
- Execute `bundle install` to update the lockfile
|
425
450
|
- Commit these changes & include them in your PR.
|
426
451
|
|
427
452
|
After merging your PR:
|
428
453
|
|
429
|
-
- Check out `
|
454
|
+
- Check out `main` and pull to get the latest.
|
455
|
+
|
456
|
+
Update the following in AC side, the commits are to be made from AC for the files mentioned:
|
457
|
+
|
458
|
+
- 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.
|
430
459
|
<!--
|
431
460
|
- Run `bundle exec rake release`.
|
432
461
|
_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
CHANGED
data/lib/alula/resources/user.rb
CHANGED
@@ -17,7 +17,7 @@ module Alula
|
|
17
17
|
relationship :address, type: 'users-addresses', cardinality: 'To-one'
|
18
18
|
relationship :pushtokens, type: 'users-pushtokens', cardinality: 'To-many'
|
19
19
|
relationship :preferences, type: 'users-preferences', cardinality: 'To-one'
|
20
|
-
relationship :
|
20
|
+
relationship :users_video_profile, type: 'users-videoprofiles', cardinality: 'To-many'
|
21
21
|
|
22
22
|
# Resource Fields
|
23
23
|
# Not all params are used at the moment. See Alula::ResourceAttributes for details
|
@@ -34,5 +34,12 @@ module Alula
|
|
34
34
|
filterable: false,
|
35
35
|
creatable_by: [:system, :station, :dealer, :technician],
|
36
36
|
patchable_by: [:system, :station, :dealer, :technician]
|
37
|
+
|
38
|
+
field :vendors,
|
39
|
+
type: :array,
|
40
|
+
sortable: false,
|
41
|
+
filterable: false,
|
42
|
+
creatable_by: [:system, :station, :dealer, :technician],
|
43
|
+
patchable_by: [:system, :station, :dealer, :technician]
|
37
44
|
end
|
38
45
|
end
|
data/lib/alula/version.rb
CHANGED
metadata
CHANGED
@@ -1,14 +1,14 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: alula-ruby
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 0.69.
|
4
|
+
version: 0.69.4
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Titus Johnson
|
8
8
|
autorequire:
|
9
9
|
bindir: exe
|
10
10
|
cert_chain: []
|
11
|
-
date: 2023-01-
|
11
|
+
date: 2023-01-26 00:00:00.000000000 Z
|
12
12
|
dependencies:
|
13
13
|
- !ruby/object:Gem::Dependency
|
14
14
|
name: httparty
|