google-cloud-resource_manager 0.39.0 → 1.0.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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: c21268e2e50572d7de98db76d31b02d3541f45ee62ad94b9dd78933dbdc96b13
4
- data.tar.gz: 94f67d43a0e67d9622d397cd098af612231bf03b674c20a5a072201c3e6a76e6
3
+ metadata.gz: 7d7ec9b1479afc7612391e3c799bdac9582e4e4031b3c08be7465c1390ba09ae
4
+ data.tar.gz: f5ca29c366df7e4fbf67991d2cd3ec2b2c53b7585d90195f9f0ac9c1f43159b5
5
5
  SHA512:
6
- metadata.gz: 1af6f7c2108fe7ac7e3af386086515636039ed4426ba85fcdf873b75aaa9588e19bd985229cc4e872d9155d41b3a0ea0eb17b1b3253d92c8989e1ee181ca7b36
7
- data.tar.gz: 54451d21e273896425e4bf1898b09605bb2086eafa5aa20ac5ae438c6dbb1522f5202e36252f74a2dd230ac14501c7b292985d50ea7f7262ffbb1ab8d3565959
6
+ metadata.gz: fa17b3e6065d7a1c4a8712a3d2c38db1abe46553268f147781b70e4365c31bc7c35949c684366dc01f0d3681951b18d80eea19163bba78541c1dbb6dca86e5f3
7
+ data.tar.gz: ae23e35b4998944586881e9d79feac1a2bee5a66185e217aa0403ef78b8ea4b10c4be931752a982d5d1396c22f116ddfbd4ec3710e4702acf7dc99c731d05f47
data/.yardopts CHANGED
@@ -1,16 +1,12 @@
1
1
  --no-private
2
- --title=Google Cloud Resource Manager
2
+ --title="Cloud Resource Manager API"
3
+ --exclude _pb\.rb$
3
4
  --markup markdown
4
5
  --markup-provider redcarpet
5
- --main OVERVIEW.md
6
6
 
7
7
  ./lib/**/*.rb
8
8
  -
9
- OVERVIEW.md
9
+ README.md
10
10
  AUTHENTICATION.md
11
- LOGGING.md
12
- CONTRIBUTING.md
13
- TROUBLESHOOTING.md
14
- CHANGELOG.md
15
- CODE_OF_CONDUCT.md
16
- LICENSE
11
+ MIGRATING.md
12
+ LICENSE.md
data/AUTHENTICATION.md CHANGED
@@ -1,182 +1,122 @@
1
1
  # Authentication
2
2
 
3
- In general, the google-cloud-resource_manager library uses [Service
4
- Account](https://cloud.google.com/iam/docs/creating-managing-service-accounts)
5
- credentials to connect to Google Cloud services. When running on Google Cloud
6
- Platform (GCP), including Google Compute Engine (GCE), Google Kubernetes Engine
7
- (GKE), Google App Engine (GAE), Google Cloud Functions (GCF) and Cloud Run,
8
- the credentials will be discovered automatically. When running on other
9
- environments, the Service Account credentials can be specified by providing the
10
- path to the [JSON
11
- keyfile](https://cloud.google.com/iam/docs/managing-service-account-keys) for
12
- the account (or the JSON itself) in environment variables. Additionally, Cloud
13
- SDK credentials can also be discovered automatically, but this is only
14
- recommended during development.
15
-
16
- ## Project and Credential Lookup
17
-
18
- The google-cloud-resource_manager library aims to make authentication as simple
19
- as possible, and provides several mechanisms to configure your system without
20
- providing **Project ID** and **Service Account Credentials** directly in code.
21
-
22
- **Project ID** is discovered in the following order:
23
-
24
- 1. Specify project ID in method arguments
25
- 2. Specify project ID in configuration
26
- 3. Discover project ID in environment variables
27
- 4. Discover GCE project ID
28
-
29
- **Credentials** are discovered in the following order:
30
-
31
- 1. Specify credentials in method arguments
32
- 2. Specify credentials in configuration
33
- 3. Discover credentials path in environment variables
34
- 4. Discover credentials JSON in environment variables
35
- 5. Discover credentials file in the Cloud SDK's path
36
- 6. Discover GCE credentials
3
+ The recommended way to authenticate to the google-cloud-resource_manager library is to use
4
+ [Application Default Credentials (ADC)](https://cloud.google.com/docs/authentication/application-default-credentials).
5
+ To review all of your authentication options, see [Credentials lookup](#credential-lookup).
37
6
 
38
- ### Google Cloud Platform environments
7
+ ## Quickstart
39
8
 
40
- While running on Google Cloud Platform environments such as Google Compute
41
- Engine, Google App Engine and Google Kubernetes Engine, no extra work is needed.
42
- The **Project ID** and **Credentials** and are discovered automatically. Code
43
- should be written as if already authenticated. Just be sure when you [set up the
44
- GCE instance][gce-how-to], you add the correct scopes for the APIs you want to
45
- access. For example:
46
-
47
- * **All APIs**
48
- * `https://www.googleapis.com/auth/cloud-platform`
49
- * `https://www.googleapis.com/auth/cloud-platform.read-only`
50
- * **BigQuery**
51
- * `https://www.googleapis.com/auth/bigquery`
52
- * `https://www.googleapis.com/auth/bigquery.insertdata`
53
- * **Compute Engine**
54
- * `https://www.googleapis.com/auth/compute`
55
- * **Datastore**
56
- * `https://www.googleapis.com/auth/datastore`
57
- * `https://www.googleapis.com/auth/userinfo.email`
58
- * **DNS**
59
- * `https://www.googleapis.com/auth/ndev.clouddns.readwrite`
60
- * **Pub/Sub**
61
- * `https://www.googleapis.com/auth/pubsub`
62
- * **Storage**
63
- * `https://www.googleapis.com/auth/devstorage.full_control`
64
- * `https://www.googleapis.com/auth/devstorage.read_only`
65
- * `https://www.googleapis.com/auth/devstorage.read_write`
9
+ The following example shows how to set up authentication for a local development
10
+ environment with your user credentials.
66
11
 
67
- ### Environment Variables
12
+ **NOTE:** This method is _not_ recommended for running in production. User credentials
13
+ should be used only during development.
68
14
 
69
- The **Project ID** and **Credentials JSON** can be placed in environment
70
- variables instead of declaring them directly in code. Each service has its own
71
- environment variable, allowing for different service accounts to be used for
72
- different services. (See the READMEs for the individual service gems for
73
- details.) The path to the **Credentials JSON** file can be stored in the
74
- environment variable, or the **Credentials JSON** itself can be stored for
75
- environments such as Docker containers where writing files is difficult or not
76
- encouraged.
15
+ 1. [Download and install the Google Cloud CLI](https://cloud.google.com/sdk).
16
+ 2. Set up a local ADC file with your user credentials:
77
17
 
78
- The environment variables that Resource Manager checks for project ID are:
18
+ ```sh
19
+ gcloud auth application-default login
20
+ ```
79
21
 
80
- 1. `RESOURCE_MANAGER_PROJECT`
81
- 2. `GOOGLE_CLOUD_PROJECT`
22
+ 3. Write code as if already authenticated.
82
23
 
83
- The environment variables that Resource Manager checks for credentials are
84
- configured on {Google::Cloud::ResourceManager::Credentials}:
24
+ For more information about setting up authentication for a local development environment, see
25
+ [Set up Application Default Credentials](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-dev).
85
26
 
86
- 1. `RESOURCE_MANAGER_CREDENTIALS` - Path to JSON file, or JSON contents
87
- 2. `RESOURCE_MANAGER_KEYFILE` - Path to JSON file, or JSON contents
88
- 3. `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
89
- 4. `GOOGLE_CLOUD_KEYFILE` - Path to JSON file, or JSON contents
90
- 5. `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
27
+ ## Credential Lookup
91
28
 
92
- ```ruby
93
- require "google/cloud/resource_manager"
29
+ The google-cloud-resource_manager library provides several mechanisms to configure your system.
30
+ Generally, using Application Default Credentials to facilitate automatic
31
+ credentials discovery is the easist method. But if you need to explicitly specify
32
+ credentials, there are several methods available to you.
94
33
 
95
- ENV["RESOURCE_MANAGER_PROJECT"] = "my-project-id"
96
- ENV["RESOURCE_MANAGER_CREDENTIALS"] = "path/to/keyfile.json"
34
+ Credentials are accepted in the following ways, in the following order or precedence:
97
35
 
98
- resource_manager = Google::Cloud::ResourceManager.new
99
- ```
36
+ 1. Credentials specified in method arguments
37
+ 2. Credentials specified in configuration
38
+ 3. Credentials pointed to or included in environment variables
39
+ 4. Credentials found in local ADC file
40
+ 5. Credentials returned by the metadata server for the attached service account (GCP)
100
41
 
101
42
  ### Configuration
102
43
 
103
- The **Project ID** and the path to the **Credentials JSON** file can be configured
104
- instead of placing them in environment variables or providing them as arguments.
44
+ You can configure a path to a JSON credentials file, either for an individual client object or
45
+ globally, for all client objects. The JSON file can contain credentials created for
46
+ [workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
47
+ [workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
48
+ [service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
49
+
50
+ Note: Service account keys are a security risk if not managed correctly. You should
51
+ [choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
52
+ whenever possible.
53
+
54
+ To configure a credentials file for an individual client initialization:
105
55
 
106
56
  ```ruby
107
57
  require "google/cloud/resource_manager"
108
58
 
109
- Google::Cloud::ResourceManager.configure do |config|
110
- config.project_id = "my-project-id"
111
- config.credentials = "path/to/keyfile.json"
59
+ client = Google::Cloud::ResourceManager.folders do |config|
60
+ config.credentials = "path/to/credentialfile.json"
112
61
  end
113
-
114
- resource_manager = Google::Cloud::ResourceManager.new
115
62
  ```
116
63
 
117
- ### Cloud SDK
64
+ To configure a credentials file globally for all clients:
118
65
 
119
- This option allows for an easy way to authenticate during development. If
120
- credentials are not provided in code or in environment variables, then Cloud SDK
121
- credentials are discovered.
122
-
123
- To configure your system for this, simply:
124
-
125
- 1. [Download and install the Cloud SDK](https://cloud.google.com/sdk)
126
- 2. Authenticate using OAuth 2.0 `$ gcloud auth login`
127
- 3. Write code as if already authenticated.
128
-
129
- **NOTE:** This is _not_ recommended for running in production. The Cloud SDK
130
- *should* only be used during development.
131
-
132
- [gce-how-to]: https://cloud.google.com/compute/docs/authentication#using
133
- [dev-console]: https://console.cloud.google.com/project
134
-
135
- [enable-apis]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/enable-apis.png
66
+ ```ruby
67
+ require "google/cloud/resource_manager"
136
68
 
137
- [create-new-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account.png
138
- [create-new-service-account-existing-keys]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/create-new-service-account-existing-keys.png
139
- [reuse-service-account]: https://raw.githubusercontent.com/GoogleCloudPlatform/gcloud-common/master/authentication/reuse-service-account.png
69
+ Google::Cloud::ResourceManager.configure do |config|
70
+ config.credentials = "path/to/credentialfile.json"
71
+ end
140
72
 
141
- ## Creating a Service Account
73
+ client = Google::Cloud::ResourceManager.folders
74
+ ```
142
75
 
143
- Google Cloud requires a **Project ID** and **Service Account Credentials** to
144
- connect to the APIs. You will use the **Project ID** and **JSON key file** to
145
- connect to most services with google-cloud-resource_manager.
76
+ ### Environment Variables
146
77
 
147
- If you are not running this client on Google Compute Engine, you need a Google
148
- Developers service account.
78
+ You can also use an environment variable to provide a JSON credentials file.
79
+ The environment variable can contain a path to the credentials file or, for
80
+ environments such as Docker containers where writing files is not encouraged,
81
+ you can include the credentials file itself.
149
82
 
150
- 1. Visit the [Google Developers Console][dev-console].
151
- 1. Create a new project or click on an existing project.
152
- 1. Activate the slide-out navigation tray and select **API Manager**. From
153
- here, you will enable the APIs that your application requires.
83
+ The JSON file can contain credentials created for
84
+ [workload identity federation](https://cloud.google.com/iam/docs/workload-identity-federation),
85
+ [workforce identity federation](https://cloud.google.com/iam/docs/workforce-identity-federation), or a
86
+ [service account key](https://cloud.google.com/docs/authentication/provide-credentials-adc#local-key).
154
87
 
155
- ![Enable the APIs that your application requires][enable-apis]
88
+ Note: Service account keys are a security risk if not managed correctly. You should
89
+ [choose a more secure alternative to service account keys](https://cloud.google.com/docs/authentication#auth-decision-tree)
90
+ whenever possible.
156
91
 
157
- *Note: You may need to enable billing in order to use these services.*
92
+ The environment variables that google-cloud-resource_manager
93
+ checks for credentials are:
158
94
 
159
- 1. Select **Credentials** from the side navigation.
95
+ * `GOOGLE_CLOUD_CREDENTIALS` - Path to JSON file, or JSON contents
96
+ * `GOOGLE_APPLICATION_CREDENTIALS` - Path to JSON file
160
97
 
161
- You should see a screen like one of the following.
98
+ ```ruby
99
+ require "google/cloud/resource_manager"
162
100
 
163
- ![Create a new service account][create-new-service-account]
101
+ ENV["GOOGLE_APPLICATION_CREDENTIALS"] = "path/to/credentialfile.json"
164
102
 
165
- ![Create a new service account With Existing Keys][create-new-service-account-existing-keys]
103
+ client = Google::Cloud::ResourceManager.folders
104
+ ```
166
105
 
167
- Find the "Add credentials" drop down and select "Service account" to be
168
- guided through downloading a new JSON key file.
106
+ ### Local ADC file
169
107
 
170
- If you want to re-use an existing service account, you can easily generate a
171
- new key file. Just select the account you wish to re-use, and click "Generate
172
- new JSON key":
108
+ You can set up a local ADC file with your user credentials for authentication during
109
+ development. If credentials are not provided in code or in environment variables,
110
+ then the local ADC credentials are discovered.
173
111
 
174
- ![Re-use an existing service account][reuse-service-account]
112
+ Follow the steps in [Quickstart](#quickstart) to set up a local ADC file.
175
113
 
176
- The key file you download will be used by this library to authenticate API
177
- requests and should be stored in a secure location.
114
+ ### Google Cloud Platform environments
178
115
 
179
- ## Troubleshooting
116
+ When running on Google Cloud Platform (GCP), including Google Compute Engine
117
+ (GCE), Google Kubernetes Engine (GKE), Google App Engine (GAE), Google Cloud
118
+ Functions (GCF) and Cloud Run, credentials are retrieved from the attached
119
+ service account automatically. Code should be written as if already authenticated.
180
120
 
181
- If you're having trouble authenticating you can ask for help by following the
182
- {file:TROUBLESHOOTING.md Troubleshooting Guide}.
121
+ For more information, see
122
+ [Set up ADC for Google Cloud services](https://cloud.google.com/docs/authentication/provide-credentials-adc#attached-sa).
data/LICENSE.md ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.