cloud_events 0.1.0
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 +7 -0
- data/.yardopts +11 -0
- data/CHANGELOG.md +5 -0
- data/LICENSE.md +203 -0
- data/README.md +250 -0
- data/lib/cloud_events.rb +31 -0
- data/lib/cloud_events/content_type.rb +208 -0
- data/lib/cloud_events/errors.rb +28 -0
- data/lib/cloud_events/event.rb +69 -0
- data/lib/cloud_events/event/field_interpreter.rb +136 -0
- data/lib/cloud_events/event/v0.rb +221 -0
- data/lib/cloud_events/event/v1.rb +208 -0
- data/lib/cloud_events/http_binding.rb +292 -0
- data/lib/cloud_events/json_format.rb +158 -0
- data/lib/cloud_events/version.rb +9 -0
- metadata +63 -0
checksums.yaml
ADDED
@@ -0,0 +1,7 @@
|
|
1
|
+
---
|
2
|
+
SHA256:
|
3
|
+
metadata.gz: 8c1658e90d1e5d2ba5fe59cd174faf0bf1a475e14f9d910fab5a5136b13417fd
|
4
|
+
data.tar.gz: 19dfdc7de4c50ea3e03cb7818ed526b9bff93173be68d378c512b4c466fc14ab
|
5
|
+
SHA512:
|
6
|
+
metadata.gz: 1ff3c4b897ad25aafe2a13761d862d3bca6f28d2d9d57f611f3bf2c086161c6b559d30125888654b6e543ce30ffa7bedff99c42f115871507480855264354cea
|
7
|
+
data.tar.gz: 35024a3f6613d3d24a71f56fe50e3dc8a3e53a53c6b79468fd3a9f61b7311b940a1bff1d6dfb63000c37bd653e96ee9007c9f4d30e201060186f6b5766fd6515
|
data/.yardopts
ADDED
data/CHANGELOG.md
ADDED
data/LICENSE.md
ADDED
@@ -0,0 +1,203 @@
|
|
1
|
+
Apache License
|
2
|
+
==============
|
3
|
+
|
4
|
+
* Version 2.0, January 2004
|
5
|
+
* https://www.apache.org/licenses/
|
6
|
+
|
7
|
+
### TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
8
|
+
|
9
|
+
1. **Definitions.**
|
10
|
+
|
11
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
12
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
13
|
+
|
14
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
15
|
+
the copyright owner that is granting the License.
|
16
|
+
|
17
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
18
|
+
other entities that control, are controlled by, or are under common
|
19
|
+
control with that entity. For the purposes of this definition,
|
20
|
+
"control" means (i) the power, direct or indirect, to cause the
|
21
|
+
direction or management of such entity, whether by contract or
|
22
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
23
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
24
|
+
|
25
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
26
|
+
exercising permissions granted by this License.
|
27
|
+
|
28
|
+
"Source" form shall mean the preferred form for making modifications,
|
29
|
+
including but not limited to software source code, documentation
|
30
|
+
source, and configuration files.
|
31
|
+
|
32
|
+
"Object" form shall mean any form resulting from mechanical
|
33
|
+
transformation or translation of a Source form, including but
|
34
|
+
not limited to compiled object code, generated documentation,
|
35
|
+
and conversions to other media types.
|
36
|
+
|
37
|
+
"Work" shall mean the work of authorship, whether in Source or
|
38
|
+
Object form, made available under the License, as indicated by a
|
39
|
+
copyright notice that is included in or attached to the work
|
40
|
+
(an example is provided in the Appendix below).
|
41
|
+
|
42
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
43
|
+
form, that is based on (or derived from) the Work and for which the
|
44
|
+
editorial revisions, annotations, elaborations, or other modifications
|
45
|
+
represent, as a whole, an original work of authorship. For the purposes
|
46
|
+
of this License, Derivative Works shall not include works that remain
|
47
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
48
|
+
the Work and Derivative Works thereof.
|
49
|
+
|
50
|
+
"Contribution" shall mean any work of authorship, including
|
51
|
+
the original version of the Work and any modifications or additions
|
52
|
+
to that Work or Derivative Works thereof, that is intentionally
|
53
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
54
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
55
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
56
|
+
means any form of electronic, verbal, or written communication sent
|
57
|
+
to the Licensor or its representatives, including but not limited to
|
58
|
+
communication on electronic mailing lists, source code control systems,
|
59
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
60
|
+
Licensor for the purpose of discussing and improving the Work, but
|
61
|
+
excluding communication that is conspicuously marked or otherwise
|
62
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
63
|
+
|
64
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
65
|
+
on behalf of whom a Contribution has been received by Licensor and
|
66
|
+
subsequently incorporated within the Work.
|
67
|
+
|
68
|
+
2. **Grant of Copyright License.** Subject to the terms and conditions of
|
69
|
+
this License, each Contributor hereby grants to You a perpetual,
|
70
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
71
|
+
copyright license to reproduce, prepare Derivative Works of,
|
72
|
+
publicly display, publicly perform, sublicense, and distribute the
|
73
|
+
Work and such Derivative Works in Source or Object form.
|
74
|
+
|
75
|
+
3. **Grant of Patent License.** Subject to the terms and conditions of
|
76
|
+
this License, each Contributor hereby grants to You a perpetual,
|
77
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
78
|
+
(except as stated in this section) patent license to make, have made,
|
79
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
80
|
+
where such license applies only to those patent claims licensable
|
81
|
+
by such Contributor that are necessarily infringed by their
|
82
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
83
|
+
with the Work to which such Contribution(s) was submitted. If You
|
84
|
+
institute patent litigation against any entity (including a
|
85
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
86
|
+
or a Contribution incorporated within the Work constitutes direct
|
87
|
+
or contributory patent infringement, then any patent licenses
|
88
|
+
granted to You under this License for that Work shall terminate
|
89
|
+
as of the date such litigation is filed.
|
90
|
+
|
91
|
+
4. **Redistribution.** You may reproduce and distribute copies of the
|
92
|
+
Work or Derivative Works thereof in any medium, with or without
|
93
|
+
modifications, and in Source or Object form, provided that You
|
94
|
+
meet the following conditions:
|
95
|
+
|
96
|
+
* **(a)** You must give any other recipients of the Work or
|
97
|
+
Derivative Works a copy of this License; and
|
98
|
+
|
99
|
+
* **(b)** You must cause any modified files to carry prominent notices
|
100
|
+
stating that You changed the files; and
|
101
|
+
|
102
|
+
* **(c)** You must retain, in the Source form of any Derivative Works
|
103
|
+
that You distribute, all copyright, patent, trademark, and
|
104
|
+
attribution notices from the Source form of the Work,
|
105
|
+
excluding those notices that do not pertain to any part of
|
106
|
+
the Derivative Works; and
|
107
|
+
|
108
|
+
* **(d)** If the Work includes a "NOTICE" text file as part of its
|
109
|
+
distribution, then any Derivative Works that You distribute must
|
110
|
+
include a readable copy of the attribution notices contained
|
111
|
+
within such NOTICE file, excluding those notices that do not
|
112
|
+
pertain to any part of the Derivative Works, in at least one
|
113
|
+
of the following places: within a NOTICE text file distributed
|
114
|
+
as part of the Derivative Works; within the Source form or
|
115
|
+
documentation, if provided along with the Derivative Works; or,
|
116
|
+
within a display generated by the Derivative Works, if and
|
117
|
+
wherever such third-party notices normally appear. The contents
|
118
|
+
of the NOTICE file are for informational purposes only and
|
119
|
+
do not modify the License. You may add Your own attribution
|
120
|
+
notices within Derivative Works that You distribute, alongside
|
121
|
+
or as an addendum to the NOTICE text from the Work, provided
|
122
|
+
that such additional attribution notices cannot be construed
|
123
|
+
as modifying the License.
|
124
|
+
|
125
|
+
You may add Your own copyright statement to Your modifications and
|
126
|
+
may provide additional or different license terms and conditions
|
127
|
+
for use, reproduction, or distribution of Your modifications, or
|
128
|
+
for any such Derivative Works as a whole, provided Your use,
|
129
|
+
reproduction, and distribution of the Work otherwise complies with
|
130
|
+
the conditions stated in this License.
|
131
|
+
|
132
|
+
5. **Submission of Contributions.** Unless You explicitly state otherwise,
|
133
|
+
any Contribution intentionally submitted for inclusion in the Work
|
134
|
+
by You to the Licensor shall be under the terms and conditions of
|
135
|
+
this License, without any additional terms or conditions.
|
136
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
137
|
+
the terms of any separate license agreement you may have executed
|
138
|
+
with Licensor regarding such Contributions.
|
139
|
+
|
140
|
+
6. **Trademarks.** This License does not grant permission to use the trade
|
141
|
+
names, trademarks, service marks, or product names of the Licensor,
|
142
|
+
except as required for reasonable and customary use in describing the
|
143
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
144
|
+
|
145
|
+
7. **Disclaimer of Warranty.** Unless required by applicable law or
|
146
|
+
agreed to in writing, Licensor provides the Work (and each
|
147
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
148
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
149
|
+
implied, including, without limitation, any warranties or conditions
|
150
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
151
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
152
|
+
appropriateness of using or redistributing the Work and assume any
|
153
|
+
risks associated with Your exercise of permissions under this License.
|
154
|
+
|
155
|
+
8. **Limitation of Liability.** In no event and under no legal theory,
|
156
|
+
whether in tort (including negligence), contract, or otherwise,
|
157
|
+
unless required by applicable law (such as deliberate and grossly
|
158
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
159
|
+
liable to You for damages, including any direct, indirect, special,
|
160
|
+
incidental, or consequential damages of any character arising as a
|
161
|
+
result of this License or out of the use or inability to use the
|
162
|
+
Work (including but not limited to damages for loss of goodwill,
|
163
|
+
work stoppage, computer failure or malfunction, or any and all
|
164
|
+
other commercial damages or losses), even if such Contributor
|
165
|
+
has been advised of the possibility of such damages.
|
166
|
+
|
167
|
+
9. **Accepting Warranty or Additional Liability.** While redistributing
|
168
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
169
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
170
|
+
or other liability obligations and/or rights consistent with this
|
171
|
+
License. However, in accepting such obligations, You may act only
|
172
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
173
|
+
of any other Contributor, and only if You agree to indemnify,
|
174
|
+
defend, and hold each Contributor harmless for any liability
|
175
|
+
incurred by, or claims asserted against, such Contributor by reason
|
176
|
+
of your accepting any such warranty or additional liability.
|
177
|
+
|
178
|
+
_END OF TERMS AND CONDITIONS_
|
179
|
+
|
180
|
+
### APPENDIX: How to apply the Apache License to your work.
|
181
|
+
|
182
|
+
To apply the Apache License to your work, attach the following
|
183
|
+
boilerplate notice, with the fields enclosed by brackets "`[]`"
|
184
|
+
replaced with your own identifying information. (Don't include
|
185
|
+
the brackets!) The text should be enclosed in the appropriate
|
186
|
+
comment syntax for the file format. We also recommend that a
|
187
|
+
file or class name and description of purpose be included on the
|
188
|
+
same "printed page" as the copyright notice for easier
|
189
|
+
identification within third-party archives.
|
190
|
+
|
191
|
+
Copyright [yyyy] [name of copyright owner]
|
192
|
+
|
193
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
194
|
+
you may not use this file except in compliance with the License.
|
195
|
+
You may obtain a copy of the License at
|
196
|
+
|
197
|
+
https://www.apache.org/licenses/LICENSE-2.0
|
198
|
+
|
199
|
+
Unless required by applicable law or agreed to in writing, software
|
200
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
201
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
202
|
+
See the License for the specific language governing permissions and
|
203
|
+
limitations under the License.
|
data/README.md
ADDED
@@ -0,0 +1,250 @@
|
|
1
|
+
# Ruby SDK for [CloudEvents](https://github.com/cloudevents/spec)
|
2
|
+
|
3
|
+
## CloudEvents Ruby SDK
|
4
|
+
|
5
|
+
A [Ruby](https://ruby-lang.org) language implementation of the
|
6
|
+
[CloudEvents specification](https://github.com/cloudevents/spec).
|
7
|
+
|
8
|
+
Features:
|
9
|
+
|
10
|
+
* Ruby classes for representing CloudEvents, including support for standard
|
11
|
+
and extension attributes.
|
12
|
+
* Support for serializing and deserializing from JSON Structure Format and
|
13
|
+
JSON Batch Format.
|
14
|
+
* Support for sending and receiving CloudEvents via HTTP Bindings.
|
15
|
+
* Supports the [CloudEvent 0.3](https://github.com/cloudevents/spec/tree/v0.3)
|
16
|
+
and [CloudEvents 1.0](https://github.com/cloudevents/spec/tree/v1.0)
|
17
|
+
specifications.
|
18
|
+
* Extensible to additional formats and protocol bindings, and future
|
19
|
+
specification versions.
|
20
|
+
* Compatible with Ruby 2.4 or later, or JRuby 9.2.x or later. No runtime gem
|
21
|
+
dependencies.
|
22
|
+
|
23
|
+
## Quickstart
|
24
|
+
|
25
|
+
Install the `cloud_events` gem or add it to your bundle.
|
26
|
+
|
27
|
+
```sh
|
28
|
+
gem install cloud_events
|
29
|
+
```
|
30
|
+
|
31
|
+
### Receiving a CloudEvent in a Sinatra app
|
32
|
+
|
33
|
+
A simple [Sinatra](https://sinatrarb.com) app that receives CloudEvents:
|
34
|
+
|
35
|
+
```ruby
|
36
|
+
# examples/server/Gemfile
|
37
|
+
source "https://rubygems.org"
|
38
|
+
gem "cloud_events", "~> 0.1"
|
39
|
+
gem "sinatra", "~> 2.0"
|
40
|
+
```
|
41
|
+
|
42
|
+
```ruby
|
43
|
+
# examples/server/app.rb
|
44
|
+
require "sinatra"
|
45
|
+
require "cloud_events"
|
46
|
+
|
47
|
+
cloud_events_http = CloudEvents::HttpBinding.default
|
48
|
+
|
49
|
+
post "/" do
|
50
|
+
event = cloud_events_http.decode_rack_env request.env
|
51
|
+
logger.info "Received CloudEvent: #{event.to_h}"
|
52
|
+
end
|
53
|
+
```
|
54
|
+
|
55
|
+
### Sending a CloudEvent
|
56
|
+
|
57
|
+
A simple Ruby script that sends a CloudEvent:
|
58
|
+
|
59
|
+
```ruby
|
60
|
+
# examples/client/Gemfile
|
61
|
+
source "https://rubygems.org"
|
62
|
+
gem "cloud_events", "~> 0.1"
|
63
|
+
```
|
64
|
+
|
65
|
+
```ruby
|
66
|
+
# examples/client/send.rb
|
67
|
+
require "cloud_events"
|
68
|
+
require "net/http"
|
69
|
+
require "uri"
|
70
|
+
|
71
|
+
data = { message: "Hello, CloudEvents!" }
|
72
|
+
event = CloudEvents::Event.create spec_version: "1.0",
|
73
|
+
id: "1234-1234-1234",
|
74
|
+
source: "/mycontext",
|
75
|
+
type: "com.example.someevent",
|
76
|
+
data: data
|
77
|
+
|
78
|
+
cloud_events_http = CloudEvents::HttpBinding.default
|
79
|
+
headers, body = cloud_events_http.encode_binary_content event
|
80
|
+
Net::HTTP.post URI("http://localhost:4567"), body, headers
|
81
|
+
```
|
82
|
+
|
83
|
+
### Putting it together
|
84
|
+
|
85
|
+
Start the server on localhost:
|
86
|
+
|
87
|
+
```sh
|
88
|
+
cd server
|
89
|
+
bundle install
|
90
|
+
bundle exec ruby app.rb
|
91
|
+
```
|
92
|
+
|
93
|
+
This will run the server in the foreground and start logging to the console.
|
94
|
+
|
95
|
+
In a separate terminal shell, send it an event from the client:
|
96
|
+
|
97
|
+
```sh
|
98
|
+
cd client
|
99
|
+
bundle install
|
100
|
+
bundle exec ruby send.rb
|
101
|
+
```
|
102
|
+
|
103
|
+
The event should be logged in the server logs.
|
104
|
+
|
105
|
+
Hit `CTRL+C` to stop the server.
|
106
|
+
|
107
|
+
## Contributing
|
108
|
+
|
109
|
+
Bug reports and pull requests are welcome on GitHub at https://github.com/cloudevents/ruby-sdk.
|
110
|
+
|
111
|
+
### Development
|
112
|
+
|
113
|
+
After cloning the repo locally, install the bundle, and install the `toys` gem
|
114
|
+
if you do not already have it.
|
115
|
+
|
116
|
+
```sh
|
117
|
+
bundle install
|
118
|
+
gem install toys
|
119
|
+
```
|
120
|
+
|
121
|
+
A variety of Toys scripts are provided for running tests and builds. For
|
122
|
+
example:
|
123
|
+
|
124
|
+
```sh
|
125
|
+
# Run the unit tests
|
126
|
+
toys test
|
127
|
+
|
128
|
+
# Run CI locally, including unit tests, doc tests, and rubocop
|
129
|
+
toys ci
|
130
|
+
|
131
|
+
# Build and install the gem locally
|
132
|
+
toys install
|
133
|
+
|
134
|
+
# Clean temporary and build files
|
135
|
+
toys clean
|
136
|
+
|
137
|
+
# List all available scripts
|
138
|
+
toys
|
139
|
+
|
140
|
+
# Show online help for the "test" script
|
141
|
+
toys test --help
|
142
|
+
```
|
143
|
+
|
144
|
+
### Code style
|
145
|
+
|
146
|
+
Ruby code in this library generally follows the
|
147
|
+
[Google Ruby Style Guide](https://github.com/googleapis/ruby-style), which is
|
148
|
+
based on "Seattle Style" Ruby.
|
149
|
+
|
150
|
+
Style is enforced by Rubocop rules. You can run rubocop directly using the
|
151
|
+
`rubocop` binary:
|
152
|
+
|
153
|
+
```sh
|
154
|
+
bundle exec rubocop
|
155
|
+
```
|
156
|
+
|
157
|
+
or via Toys:
|
158
|
+
|
159
|
+
```sh
|
160
|
+
toys rubocop
|
161
|
+
```
|
162
|
+
|
163
|
+
That said, we are not style sticklers, and if a break is necessary for code
|
164
|
+
readability or practicality, Rubocop rules can be selectively disabled.
|
165
|
+
|
166
|
+
### Pull Requests
|
167
|
+
|
168
|
+
We welcome contributions from the community! Please take some time to become
|
169
|
+
acquainted with the process before submitting a pull request. There are just a
|
170
|
+
few things to keep in mind.
|
171
|
+
|
172
|
+
* **Typically a pull request should relate to an existing issue.** If you
|
173
|
+
have found a bug, want to add an improvement, or suggest an API change,
|
174
|
+
please create an issue before proceeding with a pull request. For very
|
175
|
+
minor changes such as typos in the documentation this isn't necessary.
|
176
|
+
* **Use Conventional Commit messages.** All commit messages should follow the
|
177
|
+
[Conventional Commits Specification](https://conventionalcommits.org) to
|
178
|
+
make it clear how your change should appear in release notes.
|
179
|
+
* **Sign your work.** Each PR must be signed. Be sure your git `user.name`
|
180
|
+
and `user.email` are configured then use the `--signoff` flag for your
|
181
|
+
commits. e.g. `git commit --signoff`.
|
182
|
+
* **Make sure CI passes.** Invoke `toys ci` to run the tests locally before
|
183
|
+
opening a pull request. This will include code style checks.
|
184
|
+
|
185
|
+
### Releasing
|
186
|
+
|
187
|
+
Releases can be performed only by users with write access to the repository.
|
188
|
+
|
189
|
+
To perform a release:
|
190
|
+
|
191
|
+
1. Update `lib/cloud_events/version.rb` with the new release version.
|
192
|
+
|
193
|
+
2. Add an entry to `CHANGELOG.md`. The changelog entry _must_ be headed by
|
194
|
+
the version and release date, and _must_ be consistent with the format of
|
195
|
+
previous entries.
|
196
|
+
|
197
|
+
3. Ensure the above changes are pushed to the GitHub master branch at
|
198
|
+
https://github.com/cloudevents/ruby-sdk.
|
199
|
+
|
200
|
+
4. Execute
|
201
|
+
|
202
|
+
```sh
|
203
|
+
toys release trigger $VERSION
|
204
|
+
```
|
205
|
+
|
206
|
+
where `$VERSION` is the version number (e.g. `0.1.0`). This script will
|
207
|
+
verify the version and changelog and will not proceed unless they are
|
208
|
+
correctly formatted and the master branch is up to date. It will also check
|
209
|
+
that all GitHub checks against the current commit have succeeded. If these
|
210
|
+
checks pass, the script will create and push a release tag.
|
211
|
+
|
212
|
+
5. A GitHub action will then perform the release within a few minutes. You can
|
213
|
+
check the [GitHub Actions dashboard](https://github.com/dazuma/toys/actions)
|
214
|
+
for status information on the release.
|
215
|
+
|
216
|
+
If the release workflow fails, fix the problem, and then you will need to
|
217
|
+
delete the release tag manually before triggering the release again.
|
218
|
+
|
219
|
+
## Community
|
220
|
+
|
221
|
+
* **Weekly meetings:** There are bi-weekly calls immediately following the
|
222
|
+
[Serverless/CloudEvents call](https://github.com/cloudevents/spec#meeting-time)
|
223
|
+
at 9am PT (US Pacific). Which means they will typically start at 10am PT,
|
224
|
+
but if the other call ends early then the SDK call will start early as
|
225
|
+
well. See the
|
226
|
+
[CloudEvents meeting minutes](https://docs.google.com/document/d/1OVF68rpuPK5shIHILK9JOqlZBbfe91RNzQ7u_P7YCDE/edit)
|
227
|
+
to determine which week will have the call.
|
228
|
+
|
229
|
+
* **Slack:** The `#cloudeventssdk` channel under
|
230
|
+
[CNCF's Slack workspace](https://slack.cncf.io/).
|
231
|
+
|
232
|
+
* **Email:** https://lists.cncf.io/g/cncf-cloudevents-sdk
|
233
|
+
|
234
|
+
* For additional information, contact Daniel Azuma (`@dazuma` on Slack).
|
235
|
+
|
236
|
+
## Licensing
|
237
|
+
|
238
|
+
Copyright 2020 Google LLC and the CloudEvents Ruby SDK Contributors
|
239
|
+
|
240
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
241
|
+
you may not use this software except in compliance with the License.
|
242
|
+
You may obtain a copy of the License at
|
243
|
+
|
244
|
+
https://www.apache.org/licenses/LICENSE-2.0
|
245
|
+
|
246
|
+
Unless required by applicable law or agreed to in writing, software
|
247
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
248
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
249
|
+
See the License for the specific language governing permissions and
|
250
|
+
limitations under the License.
|