bigid_auth 0.2.1.1 → 0.2.1.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 5962bef2f1558cbd897e8ce4ea968230473e47c35ff581349b087ae288fb53f3
4
- data.tar.gz: e1e6eb4d4a7abec028ad4620518e9bf364cb0768556eb016b446d7986f71503c
3
+ metadata.gz: 1ba633e86e856b290c2e52242fe614a4d0d87573594134286cf553a296d65d41
4
+ data.tar.gz: dbef81ff0214678f6121813706cd37ee853ff9959594190ddc4698accba0b4f1
5
5
  SHA512:
6
- metadata.gz: 67aba12265e0a5eba03e746f1e0d74955e31ea29a250c80c6c333aa433e10e5348f8dbba23d00b104839d9606ccffd2c3b2a4bbdd46600a146d15d4ccf684707
7
- data.tar.gz: f3883a65bc894ff5017ad9332c244fcb1d49ff3562d388d27e480baa091365a5a67ea81dd382855677fa90c9a620237bf6ccf577fab62abd4e415fdc291d7b13
6
+ metadata.gz: e779c6e506a39b4bc6ecc697a94cd216b696b55896ccb12ff07bea273859d8829ddfb6b68d7f481b77492773195a7b92e2851ccfe7ae44920634e7f6cfc37715
7
+ data.tar.gz: e1f2bcbb07df31e2709398b2e1fe9d5b92f075a66c6816584a7c8c9266896102e9adbae545e08b2be5bc3f8af779c6779774a87b8c69202bb1b2607471367bb1
@@ -1,10 +1,15 @@
1
1
  # CHANGELOG
2
2
 
3
- ## v0.2.1.1-20220209 - Danilo Carolino
3
+ ## v0.2.1.2-20220505 - [Danilo Carolino](@danilogco)
4
+
5
+ * build(deps): bump ruby version from 3.1.0 to 3.1.2
6
+
7
+ ## v0.2.1.1-20220209 - [Danilo Carolino](@danilogco)
4
8
 
5
9
  * bump flash_integration version to v0.1.2
10
+ * add docker configs to the project
6
11
 
7
- ## v0.2.1-20220202 - Danilo Carolino
12
+ ## v0.2.1-20220202 - [Danilo Carolino](@danilogco)
8
13
 
9
14
  * [QC-79](https://qflash.atlassian.net/jira/software/projects/QC/boards/31?selectedIssue=QC-79)
10
15
  Reduzir uso de pipelines em projetos Ruby [Dependabot]
@@ -0,0 +1,128 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ We as members, contributors, and leaders pledge to make participation in our
6
+ community a harassment-free experience for everyone, regardless of age, body
7
+ size, visible or invisible disability, ethnicity, sex characteristics, gender
8
+ identity and expression, level of experience, education, socio-economic status,
9
+ nationality, personal appearance, race, religion, or sexual identity
10
+ and orientation.
11
+
12
+ We pledge to act and interact in ways that contribute to an open, welcoming,
13
+ diverse, inclusive, and healthy community.
14
+
15
+ ## Our Standards
16
+
17
+ Examples of behavior that contributes to a positive environment for our
18
+ community include:
19
+
20
+ * Demonstrating empathy and kindness toward other people
21
+ * Being respectful of differing opinions, viewpoints, and experiences
22
+ * Giving and gracefully accepting constructive feedback
23
+ * Accepting responsibility and apologizing to those affected by our mistakes,
24
+ and learning from the experience
25
+ * Focusing on what is best not just for us as individuals, but for the
26
+ overall community
27
+
28
+ Examples of unacceptable behavior include:
29
+
30
+ * The use of sexualized language or imagery, and sexual attention or
31
+ advances of any kind
32
+ * Trolling, insulting or derogatory comments, and personal or political attacks
33
+ * Public or private harassment
34
+ * Publishing others' private information, such as a physical or email
35
+ address, without their explicit permission
36
+ * Other conduct which could reasonably be considered inappropriate in a
37
+ professional setting
38
+
39
+ ## Enforcement Responsibilities
40
+
41
+ Community leaders are responsible for clarifying and enforcing our standards of
42
+ acceptable behavior and will take appropriate and fair corrective action in
43
+ response to any behavior that they deem inappropriate, threatening, offensive,
44
+ or harmful.
45
+
46
+ Community leaders have the right and responsibility to remove, edit, or reject
47
+ comments, commits, code, wiki edits, issues, and other contributions that are
48
+ not aligned to this Code of Conduct, and will communicate reasons for moderation
49
+ decisions when appropriate.
50
+
51
+ ## Scope
52
+
53
+ This Code of Conduct applies within all community spaces, and also applies when
54
+ an individual is officially representing the community in public spaces.
55
+ Examples of representing our community include using an official e-mail address,
56
+ posting via an official social media account, or acting as an appointed
57
+ representative at an online or offline event.
58
+
59
+ ## Enforcement
60
+
61
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be
62
+ reported to the community leaders responsible for enforcement at
63
+ danilogcarolino@gmail.com.
64
+ All complaints will be reviewed and investigated promptly and fairly.
65
+
66
+ All community leaders are obligated to respect the privacy and security of the
67
+ reporter of any incident.
68
+
69
+ ## Enforcement Guidelines
70
+
71
+ Community leaders will follow these Community Impact Guidelines in determining
72
+ the consequences for any action they deem in violation of this Code of Conduct:
73
+
74
+ ### 1. Correction
75
+
76
+ **Community Impact**: Use of inappropriate language or other behavior deemed
77
+ unprofessional or unwelcome in the community.
78
+
79
+ **Consequence**: A private, written warning from community leaders, providing
80
+ clarity around the nature of the violation and an explanation of why the
81
+ behavior was inappropriate. A public apology may be requested.
82
+
83
+ ### 2. Warning
84
+
85
+ **Community Impact**: A violation through a single incident or series
86
+ of actions.
87
+
88
+ **Consequence**: A warning with consequences for continued behavior. No
89
+ interaction with the people involved, including unsolicited interaction with
90
+ those enforcing the Code of Conduct, for a specified period of time. This
91
+ includes avoiding interactions in community spaces as well as external channels
92
+ like social media. Violating these terms may lead to a temporary or
93
+ permanent ban.
94
+
95
+ ### 3. Temporary Ban
96
+
97
+ **Community Impact**: A serious violation of community standards, including
98
+ sustained inappropriate behavior.
99
+
100
+ **Consequence**: A temporary ban from any sort of interaction or public
101
+ communication with the community for a specified period of time. No public or
102
+ private interaction with the people involved, including unsolicited interaction
103
+ with those enforcing the Code of Conduct, is allowed during this period.
104
+ Violating these terms may lead to a permanent ban.
105
+
106
+ ### 4. Permanent Ban
107
+
108
+ **Community Impact**: Demonstrating a pattern of violation of community
109
+ standards, including sustained inappropriate behavior, harassment of an
110
+ individual, or aggression toward or disparagement of classes of individuals.
111
+
112
+ **Consequence**: A permanent ban from any sort of public interaction within
113
+ the community.
114
+
115
+ ## Attribution
116
+
117
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118
+ version 2.0, available at
119
+ <https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
120
+
121
+ Community Impact Guidelines were inspired by [Mozilla's code of conduct
122
+ enforcement ladder](https://github.com/mozilla/diversity).
123
+
124
+ [homepage]: https://www.contributor-covenant.org
125
+
126
+ For answers to common questions about this code of conduct, see the FAQ at
127
+ <https://www.contributor-covenant.org/faq>. Translations are available at
128
+ <https://www.contributor-covenant.org/translations>.
@@ -0,0 +1,14 @@
1
+ # Contributing
2
+
3
+ - Check out the latest master to make sure the feature hasn't been implemented
4
+ or the bug hasn't been fixed yet;
5
+ - Check out the issue tracker to make sure someone already hasn't requested it
6
+ and/or contributed it;
7
+ - Fork the project;
8
+ - Start a feature/bugfix branch;
9
+ - Commit and push until you are happy with your contribution;
10
+ - Make sure to add tests for it. This is important so I don't break it in a
11
+ future version unintentionally.;
12
+ - Please try not to mess with the Rakefile, version, or history. If you want to
13
+ have your own version, or is otherwise necessary, that is fine, but please
14
+ isolate to its own commit so I can cherry-pick around it.
File without changes
@@ -0,0 +1,11 @@
1
+ # Publishing
2
+
3
+ After the Github and Rubygems authenticatication, push with the following command:
4
+
5
+ ```sh
6
+ gem build bigid_auth.gemspec
7
+ rake release
8
+ gem push --key github --host https://rubygems.pkg.github.com/quasar-flash bigid_auth-0.2.1.gem
9
+ ```
10
+
11
+ Don't forget to generate the release.
@@ -9,6 +9,6 @@ module Bigid
9
9
  # Major - Incremented for incompatible changes with previous release (or big enough new features)
10
10
  # Minor - Incremented for new backwards-compatible features + deprecations
11
11
  # Patch - Incremented for backwards-compatible bug fixes
12
- VERSION = "0.2.1.1"
12
+ VERSION = "0.2.1.2"
13
13
  end
14
14
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bigid_auth
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.1.1
4
+ version: 0.2.1.2
5
5
  platform: ruby
6
6
  authors:
7
7
  - Danilo Carolino
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2022-02-09 00:00:00.000000000 Z
11
+ date: 2022-05-06 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: flash_integration
@@ -33,7 +33,7 @@ dependencies:
33
33
  version: '1.8'
34
34
  - - "<"
35
35
  - !ruby/object:Gem::Version
36
- version: '1.10'
36
+ version: '1.11'
37
37
  type: :runtime
38
38
  prerelease: false
39
39
  version_requirements: !ruby/object:Gem::Requirement
@@ -43,7 +43,7 @@ dependencies:
43
43
  version: '1.8'
44
44
  - - "<"
45
45
  - !ruby/object:Gem::Version
46
- version: '1.10'
46
+ version: '1.11'
47
47
  - !ruby/object:Gem::Dependency
48
48
  name: json
49
49
  requirement: !ruby/object:Gem::Requirement
@@ -68,58 +68,50 @@ dependencies:
68
68
  name: bundler
69
69
  requirement: !ruby/object:Gem::Requirement
70
70
  requirements:
71
- - - ">="
71
+ - - "~>"
72
72
  - !ruby/object:Gem::Version
73
- version: 1.2.0
74
- type: :development
75
- prerelease: false
76
- version_requirements: !ruby/object:Gem::Requirement
77
- requirements:
73
+ version: '2.3'
78
74
  - - ">="
79
75
  - !ruby/object:Gem::Version
80
- version: 1.2.0
81
- - !ruby/object:Gem::Dependency
82
- name: factory_bot
83
- requirement: !ruby/object:Gem::Requirement
84
- requirements:
85
- - - "~>"
86
- - !ruby/object:Gem::Version
87
- version: 6.2.0
76
+ version: 2.3.0
88
77
  type: :development
89
78
  prerelease: false
90
79
  version_requirements: !ruby/object:Gem::Requirement
91
80
  requirements:
92
81
  - - "~>"
93
82
  - !ruby/object:Gem::Version
94
- version: 6.2.0
83
+ version: '2.3'
84
+ - - ">="
85
+ - !ruby/object:Gem::Version
86
+ version: 2.3.0
95
87
  - !ruby/object:Gem::Dependency
96
- name: gemsurance
88
+ name: factory_bot
97
89
  requirement: !ruby/object:Gem::Requirement
98
90
  requirements:
99
91
  - - "~>"
100
92
  - !ruby/object:Gem::Version
101
- version: '0.10'
93
+ version: '6.2'
102
94
  type: :development
103
95
  prerelease: false
104
96
  version_requirements: !ruby/object:Gem::Requirement
105
97
  requirements:
106
98
  - - "~>"
107
99
  - !ruby/object:Gem::Version
108
- version: '0.10'
100
+ version: '6.2'
109
101
  - !ruby/object:Gem::Dependency
110
102
  name: pry
111
103
  requirement: !ruby/object:Gem::Requirement
112
104
  requirements:
113
105
  - - "~>"
114
106
  - !ruby/object:Gem::Version
115
- version: 0.14.1
107
+ version: '0.14'
116
108
  type: :development
117
109
  prerelease: false
118
110
  version_requirements: !ruby/object:Gem::Requirement
119
111
  requirements:
120
112
  - - "~>"
121
113
  - !ruby/object:Gem::Version
122
- version: 0.14.1
114
+ version: '0.14'
123
115
  - !ruby/object:Gem::Dependency
124
116
  name: rake
125
117
  requirement: !ruby/object:Gem::Requirement
@@ -129,7 +121,7 @@ dependencies:
129
121
  version: '13.0'
130
122
  - - ">="
131
123
  - !ruby/object:Gem::Version
132
- version: 10.0.0
124
+ version: '10.0'
133
125
  type: :development
134
126
  prerelease: false
135
127
  version_requirements: !ruby/object:Gem::Requirement
@@ -139,7 +131,7 @@ dependencies:
139
131
  version: '13.0'
140
132
  - - ">="
141
133
  - !ruby/object:Gem::Version
142
- version: 10.0.0
134
+ version: '10.0'
143
135
  - !ruby/object:Gem::Dependency
144
136
  name: rspec
145
137
  requirement: !ruby/object:Gem::Requirement
@@ -160,56 +152,56 @@ dependencies:
160
152
  requirements:
161
153
  - - "~>"
162
154
  - !ruby/object:Gem::Version
163
- version: 1.25.0
155
+ version: '1.28'
164
156
  type: :development
165
157
  prerelease: false
166
158
  version_requirements: !ruby/object:Gem::Requirement
167
159
  requirements:
168
160
  - - "~>"
169
161
  - !ruby/object:Gem::Version
170
- version: 1.25.0
162
+ version: '1.28'
171
163
  - !ruby/object:Gem::Dependency
172
164
  name: rubocop-packaging
173
165
  requirement: !ruby/object:Gem::Requirement
174
166
  requirements:
175
167
  - - "~>"
176
168
  - !ruby/object:Gem::Version
177
- version: 0.5.1
169
+ version: '0.5'
178
170
  type: :development
179
171
  prerelease: false
180
172
  version_requirements: !ruby/object:Gem::Requirement
181
173
  requirements:
182
174
  - - "~>"
183
175
  - !ruby/object:Gem::Version
184
- version: 0.5.1
176
+ version: '0.5'
185
177
  - !ruby/object:Gem::Dependency
186
178
  name: rubocop-performance
187
179
  requirement: !ruby/object:Gem::Requirement
188
180
  requirements:
189
181
  - - "~>"
190
182
  - !ruby/object:Gem::Version
191
- version: 1.13.2
183
+ version: '1.13'
192
184
  type: :development
193
185
  prerelease: false
194
186
  version_requirements: !ruby/object:Gem::Requirement
195
187
  requirements:
196
188
  - - "~>"
197
189
  - !ruby/object:Gem::Version
198
- version: 1.13.2
190
+ version: '1.13'
199
191
  - !ruby/object:Gem::Dependency
200
192
  name: simplecov
201
193
  requirement: !ruby/object:Gem::Requirement
202
194
  requirements:
203
195
  - - "~>"
204
196
  - !ruby/object:Gem::Version
205
- version: 0.21.2
197
+ version: '0.21'
206
198
  type: :development
207
199
  prerelease: false
208
200
  version_requirements: !ruby/object:Gem::Requirement
209
201
  requirements:
210
202
  - - "~>"
211
203
  - !ruby/object:Gem::Version
212
- version: 0.21.2
204
+ version: '0.21'
213
205
  description: A library to use BigData Corps auth features
214
206
  email:
215
207
  - danilo.carolino@qflash.com.br
@@ -217,10 +209,12 @@ executables: []
217
209
  extensions: []
218
210
  extra_rdoc_files: []
219
211
  files:
220
- - CHANGELOG.md
221
- - LICENSE.txt
222
- - README.md
223
212
  - Rakefile
213
+ - docs/CHANGELOG.md
214
+ - docs/CODE_OF_CONDUCT.md
215
+ - docs/CONTRIBUTING.md
216
+ - docs/LICENSE.txt
217
+ - docs/PUBLISHING.md
224
218
  - lib/bigid/auth/authenticated_connection.rb
225
219
  - lib/bigid/auth/authenticated_resource.rb
226
220
  - lib/bigid/auth/authentication.rb
@@ -258,7 +252,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
258
252
  - !ruby/object:Gem::Version
259
253
  version: '0'
260
254
  requirements: []
261
- rubygems_version: 3.3.3
255
+ rubygems_version: 3.3.7
262
256
  signing_key:
263
257
  specification_version: 4
264
258
  summary: Bigid Auth Library
data/README.md DELETED
@@ -1,111 +0,0 @@
1
- BigId Auth's Library for Ruby
2
- ==============
3
-
4
- [![Gem Version](https://badge.fury.io/rb/bigid_auth.svg)](https://badge.fury.io/rb/bigid_auth)
5
- [![bigid_auth](https://github.com/Quasar-Flash/bigid_auth/actions/workflows/ruby.yml/badge.svg)](https://github.com/Quasar-Flash/bigid_auth/actions/workflows/ruby.yml)
6
-
7
- Dev Requirements
8
- -----------------
9
-
10
- - Ruby: Any version
11
- - Bundler
12
-
13
- Global Installation
14
- -----------------
15
-
16
- ```ruby
17
- gem install bigid_auth
18
- ```
19
-
20
- Installation for Rails
21
- -----------------
22
-
23
- ```ruby
24
- # Add to the Gemfile
25
- gem "bigid_auth", "~> 0.2.0"
26
- ```
27
-
28
- Setting the BigID credentials - Rails Project
29
- -----------------
30
-
31
- Create the config/initializers/bigid.rb file and define:
32
-
33
- ```ruby
34
- # Set the env variables
35
- Bigid.configure do |config|
36
- config.username = "email@example.com"
37
- config.password = "xxxxxxxxx"
38
- end
39
- ```
40
-
41
- Applying an authentication
42
- -----------------
43
-
44
- ```ruby
45
- require "bigid_auth"
46
-
47
- Bigid::Auth::Authentication.new.login
48
- ```
49
-
50
- Result Example
51
- -----------------
52
-
53
- ```ruby
54
- <Flash::Integration::Response:xxxx
55
- @request=<Flash::Integration::Request:xxx
56
- @method = :post,
57
- @url = "https://accesstoken.bigdatacorp.com.br/Generate",
58
- @params = {},
59
- @headers = {
60
- :"Content-Type" => "application/json",
61
- :Accept => "application/json"
62
- },
63
- @body = "{\"login\":\"email@email.com\",\"password\":\"xxxxxx\",\"expires\":60000}",
64
- @time = 2021-07-21 22:49:57.869382432 UTC>,
65
- @status = 200,
66
- @headers = {
67
- "content-type" => "application/json",
68
- "content-length" => "361",
69
- "connection" => "keep-alive",
70
- "date" => "Wed, 21 Jul 2021 22:49:58 GMT"
71
- },
72
- @body="{\"expiration\":\"Thu, 25 May 2028 22:49:58 GMT\",\"message\":\"Token Generated\",\"success\":true,\"token\":\"xxx\",\"tokenID\":\"xxx\"}\n",
73
- @time=2021-07-21 22:49:58.248277077 UTC>
74
-
75
- ```
76
-
77
- Problems?
78
- -----------------
79
-
80
- **Please do not directly email any committers with questions or problems.** A
81
- community is best served when discussions are held in public.
82
-
83
- Searching the [issues](https://github.com/Quasar-Flash/bigid_auth/issues)
84
- for your problem is also a good idea.
85
-
86
- Contributing
87
- -----------------
88
-
89
- - Check out the latest master to make sure the feature hasn't been implemented
90
- or the bug hasn't been fixed yet;
91
- - Check out the issue tracker to make sure someone already hasn't requested it
92
- and/or contributed it;
93
- - Fork the project;
94
- - Start a feature/bugfix branch;
95
- - Commit and push until you are happy with your contribution;
96
- - Make sure to add tests for it. This is important so I don't break it in a
97
- future version unintentionally.;
98
- - Please try not to mess with the Rakefile, version, or history. If you want to
99
- have your own version, or is otherwise necessary, that is fine, but please
100
- isolate to its own commit so I can cherry-pick around it.
101
-
102
- License
103
- -----------------
104
-
105
- Please see [LICENSE](https://github.com/Quasar-Flash/bigid_auth/blob/master/LICENSE.txt)
106
- for licensing details.
107
-
108
- Authors
109
- -----------------
110
-
111
- Danilo Carolino, [@danilogco](https://github.com/danilogco) / [@Quasar-Flash](https://github.com/Quasar-Flash)