borescope 0.1.0.dev0__py3-none-any.whl

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.
@@ -0,0 +1,149 @@
1
+ """shimmer ``Runner``s that reach a workload Pebble *via the charm container*.
2
+
3
+ The obvious approach — ``juju ssh --container=<workload> <unit> …`` — does **not**
4
+ work for borescope's headline case: Juju's k8s ssh ``exec``s ``sh`` inside the target
5
+ container, so a shell-less rock fails with ``exec: "sh": not found`` (verified
6
+ against a distroless workload). The charm/operator container, however, **always has
7
+ a shell** and has every workload's Pebble socket mounted at
8
+ ``/charm/containers/<name>/pebble.socket``. So borescope lands in the *charm* container
9
+ (via ``juju ssh <unit>`` or ``juju exec -u <unit>``) and points ``pebble`` at the
10
+ workload's socket. This reaches shell-less rocks *and* stays entirely within the
11
+ user's Juju authority (no ``kubectl`` / cluster-admin).
12
+
13
+ Two runners share that pattern:
14
+
15
+ - :class:`JujuSshRunner` (default) prefixes ``juju ssh [-m <model>] <unit>``. Best
16
+ for general use; streams stdin/pty so borescope's ``exec`` / ``push`` work.
17
+ - :class:`JujuExecRunner` (``--via exec``) prefixes ``juju exec [-m <model>]
18
+ -u <unit> --``. For sites where interactive ssh is disabled but ``juju exec`` is
19
+ allowed. Request/response, so streaming commands (``logs -f``, ``exec`` with stdin)
20
+ may not behave the same.
21
+ """
22
+
23
+ from __future__ import annotations
24
+
25
+ import subprocess
26
+ from collections.abc import Mapping
27
+ from typing import IO, Any
28
+
29
+
30
+ class _JujuRunnerBase:
31
+ """Shared wrap/run/popen plumbing for the two Juju-based runners.
32
+
33
+ Subclasses just supply ``_prefix()`` — the leading ``juju ...`` argv that
34
+ reaches the charm container.
35
+ """
36
+
37
+ def __init__(
38
+ self,
39
+ unit: str,
40
+ container: str | None,
41
+ *,
42
+ model: str | None = None,
43
+ juju_binary: str = "juju",
44
+ ):
45
+ self.unit = unit
46
+ self.container = container
47
+ self.model = model
48
+ self.juju_binary = juju_binary
49
+
50
+ @property
51
+ def pebble_socket(self) -> str | None:
52
+ """The workload's Pebble socket as mounted in the charm container."""
53
+ if not self.container:
54
+ return None
55
+ return f"/charm/containers/{self.container}/pebble.socket"
56
+
57
+ def _prefix(self) -> list[str]:
58
+ raise NotImplementedError
59
+
60
+ def _remote_env_shim(self) -> list[str]:
61
+ socket = self.pebble_socket
62
+ if not socket:
63
+ return []
64
+ return [
65
+ "env",
66
+ f"PEBBLE_SOCKET={socket}",
67
+ f"PEBBLE=/charm/containers/{self.container}",
68
+ ]
69
+
70
+ def wrap(self, argv: list[str]) -> list[str]:
71
+ """Build the full local argv (juju prefix + env shim + pebble argv)."""
72
+ return [*self._prefix(), *self._remote_env_shim(), *argv]
73
+
74
+ def run(
75
+ self,
76
+ argv: list[str],
77
+ *,
78
+ input: str | None = None,
79
+ timeout: float | None = None,
80
+ env: Mapping[str, str] | None = None, # noqa: ARG002 - socket comes from container
81
+ check: bool = True,
82
+ ) -> subprocess.CompletedProcess[Any]:
83
+ return subprocess.run(
84
+ self.wrap(argv),
85
+ input=input,
86
+ # Detach stdin unless we're sending input: otherwise `juju ssh` drains
87
+ # borescope's piped-batch command stream (see juju.run_juju).
88
+ stdin=subprocess.DEVNULL if input is None else None,
89
+ capture_output=True,
90
+ text=True,
91
+ timeout=timeout,
92
+ check=check,
93
+ )
94
+
95
+ def popen(
96
+ self,
97
+ argv: list[str],
98
+ *,
99
+ stdin: int | IO[Any] | None,
100
+ stdout: int | IO[Any] | None,
101
+ stderr: int | IO[Any] | None,
102
+ text: bool,
103
+ env: Mapping[str, str] | None = None, # noqa: ARG002 - socket comes from container
104
+ ) -> subprocess.Popen[Any]:
105
+ return subprocess.Popen(
106
+ self.wrap(argv),
107
+ stdin=stdin,
108
+ stdout=stdout,
109
+ stderr=stderr,
110
+ text=text,
111
+ )
112
+
113
+
114
+ class JujuSshRunner(_JujuRunnerBase):
115
+ """Run a ``pebble`` argv against *container*'s Pebble, via ``juju ssh``.
116
+
117
+ No ``--`` separator is used: juju's k8s ssh leaks it into the remote shell. juju
118
+ passes everything after the unit to ``sh -c`` in the (charm) container and does
119
+ not flag-parse it, so the remote pebble's own flags pass through.
120
+ """
121
+
122
+ def _prefix(self) -> list[str]:
123
+ cmd = [self.juju_binary, "ssh"]
124
+ if self.model:
125
+ cmd += ["-m", self.model]
126
+ # No --container: land in the charm container (which has a shell) and reach
127
+ # the workload's Pebble through its mounted socket.
128
+ cmd.append(self.unit)
129
+ return cmd
130
+
131
+
132
+ class JujuExecRunner(_JujuRunnerBase):
133
+ """Run a ``pebble`` argv against *container*'s Pebble, via ``juju exec``.
134
+
135
+ Useful when interactive ``juju ssh`` is disabled by site policy but ``juju
136
+ exec`` is allowed. Caveat: ``juju exec`` is request/response, not a streaming
137
+ channel — so streaming commands (``logs -f``, ``exec`` with interactive stdin,
138
+ ``push`` from a non-EOF source) may not work the same as over ssh.
139
+
140
+ Uses the ``--`` separator (which ``juju exec`` accepts, unlike k8s ssh) so the
141
+ command's own flags don't get parsed by ``juju exec`` itself.
142
+ """
143
+
144
+ def _prefix(self) -> list[str]:
145
+ cmd = [self.juju_binary, "exec"]
146
+ if self.model:
147
+ cmd += ["-m", self.model]
148
+ cmd += ["-u", self.unit, "--"]
149
+ return cmd
@@ -0,0 +1,29 @@
1
+ """SocketTransport — the secondary / opportunistic backend.
2
+
3
+ Wraps the real ``ops.pebble.Client`` (HTTP API over the unix socket). It is the
4
+ fast, structured path, used only when the Pebble socket is *directly* reachable —
5
+ borescope running inside the charm, a local Pebble, or once a pushed socket relay
6
+ exists. The discovery spike showed the socket is not reachable from a laptop
7
+ against a remote cluster without extra plumbing, so for remote use the CLI relay
8
+ (:mod:`borescope.transport.cli_transport`) is the default.
9
+ """
10
+
11
+ from __future__ import annotations
12
+
13
+ from typing import TYPE_CHECKING, cast
14
+
15
+ if TYPE_CHECKING:
16
+ from . import Transport
17
+
18
+ DEFAULT_TIMEOUT = 5.0
19
+
20
+
21
+ def build_socket_transport(
22
+ socket_path: str,
23
+ *,
24
+ timeout: float = DEFAULT_TIMEOUT,
25
+ ) -> Transport:
26
+ """Build a direct-socket transport against the Pebble at *socket_path*."""
27
+ from ops import pebble # lazy: keep ops off the cold-start path
28
+
29
+ return cast("Transport", pebble.Client(socket_path=socket_path, timeout=timeout))
@@ -0,0 +1,100 @@
1
+ Metadata-Version: 2.4
2
+ Name: borescope
3
+ Version: 0.1.0.dev0
4
+ Summary: A natural shell for debugging Juju Kubernetes workload containers via Pebble
5
+ Project-URL: Homepage, https://github.com/tonyandrewmeyer/borescope
6
+ Project-URL: Repository, https://github.com/tonyandrewmeyer/borescope
7
+ Project-URL: Bug Tracker, https://github.com/tonyandrewmeyer/borescope/issues
8
+ Author-email: Tony Meyer <borescope@aotearoa.dev>
9
+ License-Expression: Apache-2.0
10
+ License-File: LICENSE
11
+ Keywords: charm,debugging,juju,kubernetes,pebble,shell
12
+ Classifier: Development Status :: 3 - Alpha
13
+ Classifier: Environment :: Console
14
+ Classifier: Intended Audience :: Developers
15
+ Classifier: Intended Audience :: System Administrators
16
+ Classifier: License :: OSI Approved :: Apache Software License
17
+ Classifier: Operating System :: POSIX :: Linux
18
+ Classifier: Programming Language :: Python :: 3
19
+ Classifier: Programming Language :: Python :: 3.11
20
+ Classifier: Programming Language :: Python :: 3.12
21
+ Classifier: Programming Language :: Python :: 3.13
22
+ Classifier: Programming Language :: Python :: 3.14
23
+ Classifier: Topic :: System :: Systems Administration
24
+ Classifier: Topic :: Utilities
25
+ Requires-Python: >=3.11
26
+ Requires-Dist: ops<4,>=2.0.0
27
+ Requires-Dist: pebble-shimmer>=1.0.0b2
28
+ Requires-Dist: prompt-toolkit>=3.0
29
+ Requires-Dist: pyyaml>=6.0
30
+ Description-Content-Type: text/markdown
31
+
32
+ # borescope
33
+
34
+ A natural shell for debugging Juju Kubernetes **workload** containers.
35
+
36
+ Kubernetes charm workload containers usually run a [rock](https://documentation.ubuntu.com/rockcraft/)
37
+ with no shell — so when something breaks, `juju ssh --container=workload …` drops
38
+ you nowhere useful. borescope gives you a prompt that *feels* like `bash` but talks to
39
+ the container's [Pebble](https://documentation.ubuntu.com/pebble/) instead of a real shell:
40
+
41
+ ```console
42
+ $ borescope myapp/0
43
+ pebble:/# ls /var/log/myapp
44
+ pebble:/# tail -f /var/log/myapp/error.log
45
+ pebble:/# services
46
+ pebble:/# logs --follow myapp
47
+ pebble:/# plan
48
+ pebble:/# exit
49
+ ```
50
+
51
+ No setup ceremony: borescope picks up your current Juju controller/model and uses your
52
+ existing `juju` authority — if you can `juju ssh` to the unit, borescope works; if you
53
+ can't, it fails the same way.
54
+
55
+ ## Install
56
+
57
+ > v1 is under active development. For now, from a checkout:
58
+
59
+ ```console
60
+ uv tool install . # or: pipx install .
61
+ ```
62
+
63
+ ## Usage
64
+
65
+ ```console
66
+ borescope <unit> # default (first) workload container
67
+ borescope <unit> --container=<name> # a specific workload container
68
+ borescope --model <model> <unit>
69
+ borescope <unit> --command "services" # one-shot, no REPL (for scripts)
70
+ borescope <unit> --snapshot # dump container state as JSON
71
+ ```
72
+
73
+ ## How it works
74
+
75
+ borescope is three thin, independently-testable layers:
76
+
77
+ - **Transport** — talks to a Pebble. The primary backend (`CliTransport`) reaches the
78
+ workload's Pebble *through the charm container* — `juju ssh <unit>` (the charm
79
+ container always has a shell) pointed at the workload's socket, which Juju mounts
80
+ there at `/charm/containers/<name>/pebble.socket`. This works even against rocks
81
+ with **no shell** (the shell lives in the charm container, not the rock) and stays
82
+ entirely within your Juju authority — no `kubectl` or cluster-admin. It drives
83
+ `pebble` via [shimmer](https://github.com/tonyandrewmeyer/shimmer) (a drop-in
84
+ `ops.pebble.Client` over the Pebble CLI). When the Pebble socket is directly
85
+ reachable (running inside the charm, or a local Pebble), `SocketTransport` uses the
86
+ real `ops.pebble.Client` HTTP API instead.
87
+ - **Discovery** — turns a unit reference into the right Pebble: confirms the unit,
88
+ reads the charm's `metadata.yaml` for workload container names, and sanity-checks
89
+ the container is alive. Everything uses your Juju model access — no `kubectl` /
90
+ cluster-admin.
91
+ - **Shell** — a small REPL: `cd`/`pwd`, path-aware tab completion, history, and a
92
+ minimal command set. Pebble's own vocabulary (`services`, `logs`, `plan`, …) is
93
+ first-class, not hidden behind a `pebble` prefix. For anything else, `exec <cmd>`
94
+ runs a binary that's already in the container.
95
+
96
+ ## Scope
97
+
98
+ borescope is for **Kubernetes** charms (which run Pebble). Machine charms already have
99
+ a real shell and are out of scope. It deliberately ships a *minimal* command set and
100
+ grows on request — if a tool exists in the container, reach it with `exec`.
@@ -0,0 +1,32 @@
1
+ borescope/__init__.py,sha256=xnX-_B7nF8uCzeafMMaPIx73NmNF0AGbFkx3bicsDoY,337
2
+ borescope/__main__.py,sha256=6fv9Gmiu9eBjT8kzhnGlTrzEtlHaupvTkjn4zR4p3zc,163
3
+ borescope/cli.py,sha256=SWDastGJboIqtMiIwm2p2DPcarw8HhKOD0AXEu8mOAQ,4157
4
+ borescope/discovery.py,sha256=5j3ZDcNaaoAY-1UvkPy6lTOYs8GVG4Klqh6ExidEevA,9297
5
+ borescope/errors.py,sha256=nT0Osg4tCJQJ0rl4OZejvELti5GJgyQQWtZsDGKwcwk,680
6
+ borescope/juju.py,sha256=NrWQqQTQn5eE9mYvKp3BcUVTYAwTR7Tu5HOJGwapqKM,3078
7
+ borescope/snapshot.py,sha256=kILzg6vI1QA0CAACNEn0KJUj8loLGC6q_uoXcbgu7q0,2983
8
+ borescope/shell/__init__.py,sha256=2dIi8wYq6fGeZyxrmtEcJNAXV_mlDg1IdfhI0yzFtWk,178
9
+ borescope/shell/completion.py,sha256=AYzodTl-AxiMfNS6_bL_OQ71TwVPpQ8U0cHGpJ1Tqb0,2550
10
+ borescope/shell/context.py,sha256=wTvyNLHqPnjoJ_fR6-gYYUsj4Mnep8RZWkIWbE0xc5s,755
11
+ borescope/shell/history.py,sha256=ZrqTQ8xwB4hVhNl2OxWIKFVJDLr80t2Oxi1Q_NeTaj0,894
12
+ borescope/shell/parser.py,sha256=LTkl8GlnbPplmXiLzqBScbtEa31lfw6dCvqz-lgn_lI,2736
13
+ borescope/shell/pathutils.py,sha256=xY4vZRDU8-hjFNLi5otH5Eick-BcK6DzYJsn2vzpVhM,618
14
+ borescope/shell/repl.py,sha256=iMusxzn1opOgHKlNzUUtuM6PX5rQXoFpLzr579g7Xv4,4624
15
+ borescope/shell/theme.py,sha256=0VeWoMcw-hfnDp4VLX2NVtsK80ZKH2_y_U7ascPpwRk,810
16
+ borescope/shell/commands/__init__.py,sha256=-wrNEaa3Cu0vIn9o38A5jro_uh-MuOecs3gTFI5ZTvI,412
17
+ borescope/shell/commands/_args.py,sha256=kx5ODp8iBm054YSIGwVwxSTC5ov2RsEWyswd7ZXd7Zo,1721
18
+ borescope/shell/commands/base.py,sha256=tEaW2ZjhAuNkFgLRnQXuaW59LdgRnVa1OUm1k0KokMM,2328
19
+ borescope/shell/commands/basic.py,sha256=RYPiKhnA05Q6-XIrmPECJbWv5OS5jFc2VgsLMkCbQ8A,3189
20
+ borescope/shell/commands/execcmd.py,sha256=P7WryKfqMNFh26G7kYEurAW1fhh19R1K8YtgUcmEGYk,1127
21
+ borescope/shell/commands/filesystem.py,sha256=aauPj-mmlfvb1S75-euDJcCMrFDXlFcH5avYV2JLZCc,16928
22
+ borescope/shell/commands/pebble.py,sha256=Rd5VpuleQoglD9TIlPf7ifojZ1w7K9ke6yLELJ6Y-Zg,12853
23
+ borescope/transport/__init__.py,sha256=3sM-FOlqCTvPQ1adbUNpYlgw5ukElpxVGRlK0Fl3VuA,5375
24
+ borescope/transport/cli_transport.py,sha256=Oa_kKnsAD2v7Ma_h0VSvTfYa3YMibxUNCB0d3oIaX1c,2282
25
+ borescope/transport/relay.py,sha256=oQwiPjK-74a9kfaCWnviv9l9bV_bktFj90O8-iru_Uk,2815
26
+ borescope/transport/runner.py,sha256=NLioXB_5gBLCGL6oP8W7u4LXzYjbLqvSAG2EilC1Uv8,5395
27
+ borescope/transport/socket_transport.py,sha256=XbB0iHXg2-EtMX1R-UZ6aGOky4IHsvjVo5wroj2IAeg,1024
28
+ borescope-0.1.0.dev0.dist-info/METADATA,sha256=vhlgWLUMjjgJZHvWSaRBl48J94hg7ocZQiq8rQMTjm4,4371
29
+ borescope-0.1.0.dev0.dist-info/WHEEL,sha256=QccIxa26bgl1E6uMy58deGWi-0aeIkkangHcxk2kWfw,87
30
+ borescope-0.1.0.dev0.dist-info/entry_points.txt,sha256=Y8domCynFwzhuDknml7D1GIJj6kXY2qBQS1VuJZdunU,49
31
+ borescope-0.1.0.dev0.dist-info/licenses/LICENSE,sha256=-ZRnlqilvVmBVlFC-kLjsMw2rvb4Doa-r1kFs8D-8bU,11361
32
+ borescope-0.1.0.dev0.dist-info/RECORD,,
@@ -0,0 +1,4 @@
1
+ Wheel-Version: 1.0
2
+ Generator: hatchling 1.29.0
3
+ Root-Is-Purelib: true
4
+ Tag: py3-none-any
@@ -0,0 +1,2 @@
1
+ [console_scripts]
2
+ borescope = borescope.cli:main
@@ -0,0 +1,203 @@
1
+
2
+ Apache License
3
+ Version 2.0, January 2004
4
+ http://www.apache.org/licenses/
5
+
6
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
7
+
8
+ 1. Definitions.
9
+
10
+ "License" shall mean the terms and conditions for use, reproduction,
11
+ and distribution as defined by Sections 1 through 9 of this document.
12
+
13
+ "Licensor" shall mean the copyright owner or entity authorized by
14
+ the copyright owner that is granting the License.
15
+
16
+ "Legal Entity" shall mean the union of the acting entity and all
17
+ other entities that control, are controlled by, or are under common
18
+ control with that entity. For the purposes of this definition,
19
+ "control" means (i) the power, direct or indirect, to cause the
20
+ direction or management of such entity, whether by contract or
21
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
22
+ outstanding shares, or (iii) beneficial ownership of such entity.
23
+
24
+ "You" (or "Your") shall mean an individual or Legal Entity
25
+ exercising permissions granted by this License.
26
+
27
+ "Source" form shall mean the preferred form for making modifications,
28
+ including but not limited to software source code, documentation
29
+ source, and configuration files.
30
+
31
+ "Object" form shall mean any form resulting from mechanical
32
+ transformation or translation of a Source form, including but
33
+ not limited to compiled object code, generated documentation,
34
+ and conversions to other media types.
35
+
36
+ "Work" shall mean the work of authorship, whether in Source or
37
+ Object form, made available under the License, as indicated by a
38
+ copyright notice that is included in or attached to the work
39
+ (an example is provided in the Appendix below).
40
+
41
+ "Derivative Works" shall mean any work, whether in Source or Object
42
+ form, that is based on (or derived from) the Work and for which the
43
+ editorial revisions, annotations, elaborations, or other modifications
44
+ represent, as a whole, an original work of authorship. For the purposes
45
+ of this License, Derivative Works shall not include works that remain
46
+ separable from, or merely link (or bind by name) to the interfaces of,
47
+ the Work and Derivative Works thereof.
48
+
49
+ "Contribution" shall mean any work of authorship, including
50
+ the original version of the Work and any modifications or additions
51
+ to that Work or Derivative Works thereof, that is intentionally
52
+ submitted to Licensor for inclusion in the Work by the copyright owner
53
+ or by an individual or Legal Entity authorized to submit on behalf of
54
+ the copyright owner. For the purposes of this definition, "submitted"
55
+ means any form of electronic, verbal, or written communication sent
56
+ to the Licensor or its representatives, including but not limited to
57
+ communication on electronic mailing lists, source code control systems,
58
+ and issue tracking systems that are managed by, or on behalf of, the
59
+ Licensor for the purpose of discussing and improving the Work, but
60
+ excluding communication that is conspicuously marked or otherwise
61
+ designated in writing by the copyright owner as "Not a Contribution."
62
+
63
+ "Contributor" shall mean Licensor and any individual or Legal Entity
64
+ on behalf of whom a Contribution has been received by Licensor and
65
+ subsequently incorporated within the Work.
66
+
67
+ 2. Grant of Copyright License. Subject to the terms and conditions of
68
+ this License, each Contributor hereby grants to You a perpetual,
69
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
70
+ copyright license to reproduce, prepare Derivative Works of,
71
+ publicly display, publicly perform, sublicense, and distribute the
72
+ Work and such Derivative Works in Source or Object form.
73
+
74
+ 3. Grant of Patent License. Subject to the terms and conditions of
75
+ this License, each Contributor hereby grants to You a perpetual,
76
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
77
+ (except as stated in this section) patent license to make, have made,
78
+ use, offer to sell, sell, import, and otherwise transfer the Work,
79
+ where such license applies only to those patent claims licensable
80
+ by such Contributor that are necessarily infringed by their
81
+ Contribution(s) alone or by combination of their Contribution(s)
82
+ with the Work to which such Contribution(s) was submitted. If You
83
+ institute patent litigation against any entity (including a
84
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
85
+ or a Contribution incorporated within the Work constitutes direct
86
+ or contributory patent infringement, then any patent licenses
87
+ granted to You under this License for that Work shall terminate
88
+ as of the date such litigation is filed.
89
+
90
+ 4. Redistribution. You may reproduce and distribute copies of the
91
+ Work or Derivative Works thereof in any medium, with or without
92
+ modifications, and in Source or Object form, provided that You
93
+ meet the following conditions:
94
+
95
+ (a) You must give any other recipients of the Work or
96
+ Derivative Works a copy of this License; and
97
+
98
+ (b) You must cause any modified files to carry prominent notices
99
+ stating that You changed the files; and
100
+
101
+ (c) You must retain, in the Source form of any Derivative Works
102
+ that You distribute, all copyright, patent, trademark, and
103
+ attribution notices from the Source form of the Work,
104
+ excluding those notices that do not pertain to any part of
105
+ the Derivative Works; and
106
+
107
+ (d) If the Work includes a "NOTICE" text file as part of its
108
+ distribution, then any Derivative Works that You distribute must
109
+ include a readable copy of the attribution notices contained
110
+ within such NOTICE file, excluding those notices that do not
111
+ pertain to any part of the Derivative Works, in at least one
112
+ of the following places: within a NOTICE text file distributed
113
+ as part of the Derivative Works; within the Source form or
114
+ documentation, if provided along with the Derivative Works; or,
115
+ within a display generated by the Derivative Works, if and
116
+ wherever such third-party notices normally appear. The contents
117
+ of the NOTICE file are for informational purposes only and
118
+ do not modify the License. You may add Your own attribution
119
+ notices within Derivative Works that You distribute, alongside
120
+ or as an addendum to the NOTICE text from the Work, provided
121
+ that such additional attribution notices cannot be construed
122
+ as modifying the License.
123
+
124
+ You may add Your own copyright statement to Your modifications and
125
+ may provide additional or different license terms and conditions
126
+ for use, reproduction, or distribution of Your modifications, or
127
+ for any such Derivative Works as a whole, provided Your use,
128
+ reproduction, and distribution of the Work otherwise complies with
129
+ the conditions stated in this License.
130
+
131
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
132
+ any Contribution intentionally submitted for inclusion in the Work
133
+ by You to the Licensor shall be under the terms and conditions of
134
+ this License, without any additional terms or conditions.
135
+ Notwithstanding the above, nothing herein shall supersede or modify
136
+ the terms of any separate license agreement you may have executed
137
+ with Licensor regarding such Contributions.
138
+
139
+ 6. Trademarks. This License does not grant permission to use the trade
140
+ names, trademarks, service marks, or product names of the Licensor,
141
+ except as required for reasonable and customary use in describing the
142
+ origin of the Work and reproducing the content of the NOTICE file.
143
+
144
+ 7. Disclaimer of Warranty. Unless required by applicable law or
145
+ agreed to in writing, Licensor provides the Work (and each
146
+ Contributor provides its Contributions) on an "AS IS" BASIS,
147
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
148
+ implied, including, without limitation, any warranties or conditions
149
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
150
+ PARTICULAR PURPOSE. You are solely responsible for determining the
151
+ appropriateness of using or redistributing the Work and assume any
152
+ risks associated with Your exercise of permissions under this License.
153
+
154
+ 8. Limitation of Liability. In no event and under no legal theory,
155
+ whether in tort (including negligence), contract, or otherwise,
156
+ unless required by applicable law (such as deliberate and grossly
157
+ negligent acts) or agreed to in writing, shall any Contributor be
158
+ liable to You for damages, including any direct, indirect, special,
159
+ incidental, or consequential damages of any character arising as a
160
+ result of this License or out of the use or inability to use the
161
+ Work (including but not limited to damages for loss of goodwill,
162
+ work stoppage, computer failure or malfunction, or any and all
163
+ other commercial damages or losses), even if such Contributor
164
+ has been advised of the possibility of such damages.
165
+
166
+ 9. Accepting Warranty or Additional Liability. While redistributing
167
+ the Work or Derivative Works thereof, You may choose to offer,
168
+ and charge a fee for, acceptance of support, warranty, indemnity,
169
+ or other liability obligations and/or rights consistent with this
170
+ License. However, in accepting such obligations, You may act only
171
+ on Your own behalf and on Your sole responsibility, not on behalf
172
+ of any other Contributor, and only if You agree to indemnify,
173
+ defend, and hold each Contributor harmless for any liability
174
+ incurred by, or claims asserted against, such Contributor by reason
175
+ of your accepting any such warranty or additional liability.
176
+
177
+ END OF TERMS AND CONDITIONS
178
+
179
+ APPENDIX: How to apply the Apache License to your work.
180
+
181
+ To apply the Apache License to your work, attach the following
182
+ boilerplate notice, with the fields enclosed by brackets "[]"
183
+ replaced with your own identifying information. (Don't include
184
+ the brackets!) The text should be enclosed in the appropriate
185
+ comment syntax for the file format. We also recommend that a
186
+ file or class name and description of purpose be included on the
187
+ same "printed page" as the copyright notice for easier
188
+ identification within third-party archives.
189
+
190
+ Copyright [yyyy] [name of copyright owner]
191
+
192
+ Licensed under the Apache License, Version 2.0 (the "License");
193
+ you may not use this file except in compliance with the License.
194
+ You may obtain a copy of the License at
195
+
196
+ http://www.apache.org/licenses/LICENSE-2.0
197
+
198
+ Unless required by applicable law or agreed to in writing, software
199
+ distributed under the License is distributed on an "AS IS" BASIS,
200
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
201
+ See the License for the specific language governing permissions and
202
+ limitations under the License.
203
+