nautobot 2.0.4__py3-none-any.whl → 2.1.0b1__py3-none-any.whl

nautobot/docs/user-guide/platform-functionality/users/objectpermission.md

@@ -1,56 +0,0 @@
-# Object Permissions
-
-A permission in Nautobot represents a relationship shared by several components:
-
-* Object type(s) - One or more types of object in Nautobot
-* User(s)/Group(s) - One or more users or groups of users
-* Action(s) - The action(s) that can be performed on an object
-* Constraints - An arbitrary filter used to limit the granted action(s) to a specific subset of objects
-
-At a minimum, a permission assignment must specify one object type, one user or group, and one action. The specification of constraints is optional: A permission without any constraints specified will apply to all instances of the selected model(s).
-
-## Actions
-
-There are four core actions that can be permitted for each type of object within Nautobot, roughly analogous to the CRUD convention (create, read, update, and delete):
-
-* **View** - Retrieve an object from the database
-* **Add** - Create a new object
-* **Change** - Modify an existing object
-* **Delete** - Delete an existing object
-
-In addition to these, permissions can also grant custom actions that may be required by a specific model or plugin. For example, the `napalm_read` permission on the device model allows a user to execute NAPALM queries on a device via Nautobot's REST API. These can be specified when granting a permission in the "additional actions" field.
-
-!!! note
-    Internally, all actions granted by a permission (both built-in and custom) are stored as strings in an array field named `actions`.
-
-## Constraints
-
-Constraints are expressed as a JSON object or list representing a [Django query filter](https://docs.djangoproject.com/en/stable/ref/models/querysets/#field-lookups). This is the same syntax that you would pass to the QuerySet `filter()` method when performing a query using the Django ORM. As with query filters, double underscores can be used to traverse related objects or invoke lookup expressions. Some example queries and their corresponding definitions are shown below.
-
-All attributes defined within a single JSON object are applied with a logical AND. For example, suppose you assign a permission for the location model with the following constraints.
-
-```json
-{
-  "status__name": "Active",
-  "parent__location_type__name": "Continent",
-  "parent__name": "Americas"
-}
-```
-
-The permission will grant access only to location which have a status of "Active" **and** which are assigned to the "Americas" continent.
-
-To achieve a logical OR with a different set of constraints, define multiple objects within a list. For example, if you want to constrain the permission to VLANs with an ID between 100 and 199 _or_ a status of "reserved," do the following:
-
-```json
-[
-  {
-    "vid__gte": 100,
-    "vid__lt": 200
-  },
-  {
-    "status__name": "Reserved"
-  }
-]
-```
-
-Additionally, where multiple permissions have been assigned for an object type, their collective constraints will be merged using a logical "OR" operation.

nautobot/docs/user-guide/platform-functionality/users/token.md

@@ -1,21 +0,0 @@
-# Tokens
-
-A token is a unique identifier mapped to a Nautobot user account. Each user may have one or more tokens which he or she can use for authentication when making REST API requests. To create a token, navigate to the API tokens page under your user profile.
-
-1. Sign into Nautobot
-2. On the upper right hand corner, select your username, then _Profile_
-3. On the left hand side, under User Profile, select _API Tokens_
-4. Select **+Add a token**
-5. Leave _Key_ blank to automatically create a token, or fill one in for yourself
-6. Check or uncheck "Write enabled", as desired
-7. (Optional) Set an expiration date for this token
-8. (Optional) Add a description
-
-!!! note
-    The creation and modification of API tokens can be restricted per user by an administrator. If you don't see an option to create an API token, ask an administrator to grant you access.
-
-Each token contains a 160-bit key represented as 40 hexadecimal characters. When creating a token, you'll typically leave the key field blank so that a random key will be automatically generated. However, Nautobot allows you to specify a key in case you need to restore a previously deleted token to operation.
-
-By default, a token can be used to perform all actions via the API that a user would be permitted to do via the web UI. Deselecting the "write enabled" option will restrict API requests made with the token to read operations (e.g. GET) only.
-
-Additionally, a token can be set to expire at a specific time. This can be useful if an external client needs to be granted temporary access to Nautobot.

nautobot/docs/user-guide/platform-functionality/webhook.md

@@ -1,137 +0,0 @@
-# Webhooks
-
-A webhook is a mechanism for conveying to some external system a change that took place in Nautobot. For example, you may want to notify a monitoring system whenever the status of a device is updated in Nautobot. This can be done by creating a webhook for the device model in Nautobot and identifying the webhook receiver. When Nautobot detects a change to a device, an HTTP request containing the details of the change and who made it be sent to the specified receiver. Webhooks are configured in the web UI under Extensibility > Webhooks.
-
-## Configuration
-
-* **Name** - A unique name for the webhook. The name is not included with outbound messages.
-* **Object type(s)** - The type or types of Nautobot object that will trigger the webhook.
-* **Enabled** - If unchecked, the webhook will be inactive.
-* **Events** - A webhook may trigger on any combination of create, update, and delete events. At least one event type must be selected.
-* **HTTP method** - The type of HTTP request to send. Options include `GET`, `POST`, `PUT`, `PATCH`, and `DELETE`.
-* **URL** - The fuly-qualified URL of the request to be sent. This may specify a destination port number if needed.
-* **HTTP content type** - The value of the request's `Content-Type` header. (Defaults to `application/json`)
-* **Additional headers** - Any additional headers to include with the request (optional). Add one header per line in the format `Name: Value`. Jinja2 templating is supported for this field (see below).
-* **Body template** - The content of the request being sent (optional). Jinja2 templating is supported for this field (see below). If blank, Nautobot will populate the request body with a raw dump of the webhook context. (If the HTTP content-type is set to `application/json`, this will be formatted as a JSON object.)
-* **Secret** - A secret string used to prove authenticity of the request (optional). This will append a `X-Hook-Signature` header to the request, consisting of a HMAC (SHA-512) hex digest of the request body using the secret as the key.
-* **SSL verification** - Uncheck this option to disable validation of the receiver's SSL certificate. (Disable with caution!)
-* **CA file path** - The file path to a particular certificate authority (CA) file to use when validating the receiver's SSL certificate (optional).
-
-## Jinja2 Template Support
-
-[Jinja2 templating](https://jinja.palletsprojects.com/) is supported for the `additional_headers` and `body_template` fields. This enables the user to convey object data in the request headers as well as to craft a customized request body. Request content can be crafted to enable the direct interaction with external systems by ensuring the outgoing message is in a format the receiver expects and understands.
-
-For example, you might create a Nautobot webhook to [trigger a Slack message](https://api.slack.com/messaging/webhooks) any time an IP address is created. You can accomplish this using the following configuration:
-
-* Object type: IPAM > IP address
-* HTTP method: `POST`
-* URL: Slack incoming webhook URL
-* HTTP content type: `application/json`
-* Body template: `{"text": "IP address {{ data['address'] }} was created by {{ username }}!"}`
-
-### Available Context
-
-The following data is available as context for Jinja2 templates:
-
-* `event` - The type of event which triggered the webhook: created, updated, or deleted.
-* `model` - The Nautobot model which triggered the change.
-* `timestamp` - The time at which the event occurred (in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format).
-* `username` - The name of the user account associated with the change.
-* `request_id` - The unique request ID. This may be used to correlate multiple changes associated with a single request.
-* `data` - A serialized representation of the object _after_ the change was made. This is typically equivalent to the model's representation in Nautobot's REST API.
-
-+++ 1.3.0
-    * `snapshots` - snapshots of the serialized object state both before and after the change was made; provided as a dictionary with keys named `prechange`, `postchange` and `differences`.
-
-### Default Request Body
-
-If no body template is specified, the request body will be populated with a JSON object containing the context data. For example, a newly created Location might appear as follows:
-
-```no-highlight
-{
-    "event": "created",
-    "timestamp": "2023-02-14 12:34:56.000000+00:00",
-    "model": "location",
-    "username": "admin",
-    "request_id": "fab0a4fb-52ba-4cb4-9756-4e6a3ac05332",
-    "data": {
-        "id": "5e4f9a91-372b-46df-a50a-c26357475bee",
-        "display": "Campus A",
-        "url": "/api/dcim/locations/5e4f9a91-372b-46df-a50a-c26357475bee/",
-        "name": "Campus A",
-        "status": {
-            "display": "Active",
-            "id": "363a431c-c784-40b5-8513-758cafd174ad",
-            "url": "/api/extras/statuses/363a431c-c784-40b5-8513-758cafd174ad/",
-            "name": "Active",
-            "created": "2023-02-14T00:00:00Z",
-            "last_updated": "2023-02-14T19:40:13.216150Z"
-        },
-        ...
-    },
-    "snapshots": {
-        "prechange": null,
-        "postchange": {
-            "id": "5e4f9a91-372b-46df-a50a-c26357475bee",
-            "asn": null,
-            "url": "/api/dcim/locations/5e4f9a91-372b-46df-a50a-c26357475bee/",
-            "name": "Campus A",
-            ...
-        },
-        "differences": {
-            "removed": null,
-            "added": {
-                "id": "5e4f9a91-372b-46df-a50a-c26357475bee",
-                "asn": null,
-                "url": "/api/dcim/locations/5e4f9a91-372b-46df-a50a-c26357475bee/",
-                "name": "Campus A",
-                ...
-            }
-        }
-    }
-}
-```
-
-## Webhook Processing
-
-When a change is detected, any resulting webhooks are placed into a Redis queue for processing. This allows the user's request to complete without needing to wait for the outgoing webhook(s) to be processed. The webhooks are then extracted from the queue by the `celery worker` process and HTTP requests are sent to their respective destinations.
-
-A request is considered successful if the response has a 2XX status code; otherwise, the request is marked as having failed. Failed requests may be retried manually via the admin UI.
-
-## Troubleshooting
-
-To assist with verifying that the content of outgoing webhooks is rendered correctly, Nautobot provides a simple HTTP listener that can be run locally to receive and display webhook requests. First, modify the target URL of the desired webhook to `http://localhost:9000/`. This will instruct Nautobot to send the request to the local server on TCP port 9000. Then, start the webhook receiver service from the Nautobot root directory:
-
-```no-highlight
-nautobot-server webhook_receiver
-```
-
-Example output:
-
-```no-highlight
-Listening on port http://localhost:9000. Stop with CONTROL-C.
-```
-
-You can test the receiver itself by sending any HTTP request to it. For example:
-
-```no-highlight
-curl -X POST http://localhost:9000 --data '{"foo": "bar"}'
-```
-
-The server will print output similar to the following:
-
-```no-highlight
-[1] Tue, 07 Apr 2020 17:44:02 GMT 127.0.0.1 "POST / HTTP/1.1" 200 -
-Host: localhost:9000
-User-Agent: curl/7.58.0
-Accept: */*
-Content-Length: 14
-Content-Type: application/x-www-form-urlencoded
-
-{"foo": "bar"}
-------------
-```
-
-Note that `webhook_receiver` does not actually _do_ anything with the information received: It merely prints the request headers and body for inspection.
-
-Now, when the Nautobot webhook is triggered and processed, you should see its headers and content appear in the terminal where the webhook receiver is listening. If you don't, check that the `celery worker` process is running.

nautobot/project-static/docs/media/nautobot_application_stack_low_level.drawio

@@ -1 +0,0 @@
-<mxfile host="Electron" modified="2022-12-22T13:58:59.816Z" agent="5.0 (Macintosh; Intel Mac OS X 10_16_0) AppleWebKit/537.36 (KHTML, like Gecko) draw.io/13.7.8 Chrome/85.0.4183.121 Electron/10.1.3 Safari/537.36" etag="M1JvU6KK4nPLl2CAebJ1" version="13.7.8" type="device"><diagram id="Cio9OjLPXT8PBRMxzQun" name="Page-1">7V1bc5s6EP41eYwHENfH1E3SdJI2rTOT5OmMDLJNixEFnNj99YeruUjGYCMgrp1Ja1ZikVbfrlarFbkA4+X61oXO4gEbyLoQOGN9AT5fCALPc3LwX0jZxBRNU2LC3DWNpFJGmJh/UULkEurKNJBXqOhjbPmmUyTq2LaR7hdo0HXxe7HaDFvFpzpwjgjCRIcWSX02DX8RU1VByehfkDlfpE/mZS0uWcK0ctITbwEN/J4jgesLMHYx9uNvy/UYWaHwUrnE993sKN02zEW2X+eG58nDpXF3A8SJ8Lheqc9QQNqlGnN5g9Yq6XDSWH+TSsDFK9tAIRP+Anx6X5g+mjhQD0vfgzEPaAt/aSXFM9OyxtjCbnQvmKk60vWA7vku/o1yJVNVEiUuKDGgt9hyJ/uUdPMNuT5a50hJH28RXiLf3QRVklI5EXeCNyAm1+/Z6EkpbZEbOcAlRJggZr5lnQk1+JLItYGMlZOTsVSSMehdxhJFxrLlh30334Kvcz/qeUyaEgS3TAkaQdQKaBRmdfjPcCDq/IDLf1Y4Lbj0IqN3FVTgFWedFea4wGWIAXvqOdE11xrpGQWN5SbIfTMDtGUdjVvMVko0dgcKmPUAnvmf+Z/5n/mf+f8b/I+Ymvbe2q3r14K3J5a8PaFLb+/lTXP9/0Re5v9qG/NtrLx/nVI96oaelrTD0yLwVXCXvsGVj6c4fETsOV05ThXiMjR8/gXtOd6NksMohKfWIrgQb0hIoYFLkxUA5XbAxZfQJfIkuoBMQRcvsFpLpC2iyjHUKez6CzzHNrTuMXYS6f1Cvr9J4hchSoqyRWvTfwlvH0nJ1Wuu5PM64RxdbNILO+hNfJMgpdev+cLsvugqvdHzoetfhcGPgKBb0PNMPSXfmFbapp2j5+GVq6MKCaWBGOjOkV8lybgeMgoxFhILLrKgb74VQy6tj2uKzSOsBnV9FlmCdhZ63KcwYoXcBhrP3hDMZjOBPssY8lSWWjIEJTugkmaAp5kBlZkV4CuE2I8VGJYRED6kERAYGYGf15On0B94vAv+HVsmipTxRHRzeMpZFULtUDlrKllOh5VGSny4doK+tDO59RGbkTqtS4uGBEFCeW0QNzS5q4SObTMOBwxgpPbRrteP+xPUeXFwOs9oCIlF3z2GRuiKQQvaeuaLVa/vvt3efXuJAuw34TRw/2n7Hfn6qJ8VXDfhgfLksFXt3pAiAYazQ25uyGaK42aHwPZOkqZmLbvOqPn5A8hikwkkunpErhlIFrlNZpWqwMveWSVdxLOeViSuiL1tHCplEfeImFaCQYGbXDUnrODtfg5fmr5EhSuhNObY6pyldWXw7uzLB7TEoaCJsBX0YbhB6GMX1TOEP5Fheo3Xrw6lHkHbU6lFy2lApM6ollPWVTSdtWQ5ZamAKpkyxwIgkZaT51mZzpTxro30YzHXMnJ/RuYjNJfBPSFWp9CrxOnu8Mmu8H6/PX7Enj930SRyMSN/orylX9kvz4F2SnvYRFy29fNlHexVGBJSDZGmUqowBTKbKBJNo7YJWR1pFJmaEjyKuwx+f6xQQPqAdksp2i2Fkv+zFWheyuXZuT0hy4SQ+UTIY6gvPqKQRZUbmpDJZMHgNpRwbm3RIoU/VOlGn8Ry5ujxpx2p8yWpS3LfUpcYhLqah606ilrxWt0Fhtz2AuM41SB99cjufHe8E1IOoA1NOQDr3NpBGSMxXS90IW/q+p9XCPHmoxc2tsNwRXf2ySArBcRWtreAXNMUAW1QpgiQrlCWtVJelY+jZf3pKIxSUhipQ4WhjwbrAxb9TghlefduoKT+nKXt9qFy0Oa+qMh5H+uSG3GcusfROjy6W2nJ9ntfAzN5pPe12+RdOaflk8k9mjy6j9C+Cma6JfAgr1wjTqjeggkvygoyhIyax9e5e61/fZ/Jzgv+fis9QWNWO60O9Lb4oQ44gwXqoUN0kBEezrj2Zlarmp2zqqvnyW2Y3xRvbN+ubFPHrn1C1pTIdZcoK1zaXjYzB1Ik97L37xd35fMc7mqIpEpUYXAgjoZAO2baJvhnSN6R2aNoU66D49IqBfDUwx3bM8DtC5mW6POxhVw6L63WPZPOTsj87mT4UzzPdWr8j9tULi+Odm+KD6bJT9D7HRQ+Y/d3ISOPfbs/OlTO/M/8z/zP/M/8/w3+NHbMzp/vd6Vb8J7LBxHqvm2IoffM6gD6vlPiu7NnKU+0TBtdpgKJnhku9iTyqZXPa5qF26DSB37zQkeH40tp5xpldQ5UCvTZpTMKtIXjycT/+FKGC8/RDrN0uoOcQuCf3M8vJcBoWu+jQTtIeDLy3r7Irxf40zeXSPkOJ/7NNAEp7fnebaPUQgwlSC5UGCzu1LbfyzN0lxaKqjCpCjNO0WP9cpoaqpXLCqi/2Xu4PgLKntXA9JEOCBYJGWxTKBoNfoOd/i4GXxiUMQbkZtrJn9lQaa8q6PbMBoM0xCGpnJDXuBHXPAXrcEVMj9PtT6bp6M0mAd4K6FOUEqp2HEG/aOmUuEim5PdwPojTlCagzL1rBxTAVI0kWrpry/DiasIrDQEOZJIXGRicIxOambiFv1ZLJ3VloasfN6fXPeHRX7ozdaxlppNLsxdUHeSD9zHWtVPb1b7GWsDwD1K87+6XL8/ueDVW7l9XbJOpWb7njOeFAo6OO81QGo0DbbvKxAEAvDbS8h+x4A9ImlosruUd0F6gNuJ4gk3qdAha1UPae7kaFaQMXrf0MQ/d7Idp6+jjNXEkFxEnatJhGAt5iSSKUiBL2khWue2HbwljwWX2R5Di6tmfkgLX/wM=</diagram></mxfile>

nautobot-2.0.4.dist-info/LICENSE.txt

@@ -1,177 +0,0 @@
-
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS