| Name | jnprsr JSON |
| Version |
0.1.1
JSON |
| download |
| home_page | None |
| Summary | jnprsr is a Parser for Juniper Configuration Files |
| upload_time | 2025-02-12 15:38:52 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | 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
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
|
| keywords |
jnpr
juniper
parser
junos
configuration
config
|
| VCS |
 |
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# jnprsr
jnprsr ('ʤunəpɑrsər) is a **Parser** for **Juniper configuration files**.
It is based around a Lexer and Parser built using **ANTLR4** (https://www.antlr.org/). The formal grammar used in our project was initially created by the **batfish** (https://github.com/batfish/batfish) project.
Our tool allows to generate an **Abstract Syntax Tree (AST)** from a given Juniper configuration file.
This **AST** can then be processed further. Currently, we provide the following functions:
* **Pretty-Printing**
* **Configuration Merge**
* **Sub-Tree Selection**
The **AST** generated by our implementation uses a data-type provided by the **anytree** (https://github.com/c0fec0de/anytree) library. You can easily process the **AST** generated by our implementation and use it in our own tools.
*Please note: This is currently still a **beta release**. This product comes with absolutely no warranty. It is neither supported nor endorsed in any way by Juniper Networks Inc. We assume no liability for any undesired or incorrect behavior you might experience with this software. If you break your network using **jnprsr**, it is your responsibility and you should be ashamed of yourself for not testing your software properly.*
## Installation
You can install jnprsr using pip:
```
pip install jnprsr
```
You can also install directly from Git:
```
pip install git+https://github.com/markusju/jnprsr.git
```
## TL;DR - What you can do with jnprsr
### Pretty-Printing
It allows you to transform a configuration file looking like this
```
interfaces { et-0/0/0 {description "More Bandwidth!"; unit 0 {family inet{address 192.0.2.1/24;}}}}
```
into this
```
interfaces {
et-0/0/0 {
description "More Bandwidth!";
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
}
```
### Configuration Merge
Suppose you have this snippet
```
interfaces {
et-0/0/0 {
description "Skynet NNI";
}
}
```
and this target configuration
```
interfaces {
et-0/0/0 {
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
}
```
using **jnprsr** you can perform a `> load merge` operation on the target configuration with the snippet to generate this:
```
interfaces {
et-0/0/0 {
description "Skynet NNI";
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
}
```
### Sub-Tree Selection
Let's say you have this configuration file:
```
protocols {
bgp {
group SKYNET-PEER {
type external;
peer-as 1337;
neighbor 1.2.3.4;
}
group EVILCORP-PEER {
type external;
peer-as 1338;
neighbor 1.2.3.5;
}
group UMBRELLACORP-PEER {
type external;
peer-as 1339;
neighbor 1.2.3.6;
}
}
}
```
and you want to access the sub-tree of the *SKYNET-PEER* BGP peer-group.
Using **jnprsr** you can easily perform the equivalent of
`> show configuration protocols bgp group SKYNET-PEER`:
```
protocols {
bgp {
group SKYNET-PEER {
type external;
peer-as 1337;
neighbor 1.2.3.4;
}
}
}
```
### Other Stuff
Since **jnprsr** creates an anytree object, you can easily work with the parsed configuration data.
Some things you could do include, but are not limited to:
* Validation and/or Verification: Does a certain configuration element or sub-tree exist?
* Comparison: Comparing two given configurations, what nodes are different?
* Editing: Create, Remove, Change a given configuration and generate textual output from the changed tree again.
## Getting Started
### On the shell
**jnprsr** currently comes with 3 commands that you can use on your shell:
- jnprsr-pretty
- jnprsr-subtree
- jnprsr-merge
#### jnprsr-pretty
is a pretty printer. You can supply a Juniper Configuration file and it will [*pretty print*](https://en.wikipedia.org/wiki/Prettyprint) the received configuration. Meaning that the configuration is returned with the proper indentation and spacing.
You can use the script interactively. Simply call it and then paste the configuration. You can end your input on an empty new line with `CTRL+D` or by typing `!END`.
```
$ jnprsr-pretty
[Type CTRL+D or '!END' at a new line to end input]
interfaces { et-0/0/0 {description "More Bandwidth!"; unit 0 {family inet{address 192.0.2.1/24;}}}}
interfaces {
et-0/0/0 {
description "More Bandwidth!";
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
}
```
Alternatively you can also simply pipe your messed up config at the script to make it pretty. In this case you do not need to end the input.
Note that we are using the `-s` flag in this example. This silences any additional output, so that you can process the output more easily.
```
$ cat what-a-mess.txt | jnprsr-pretty -s
interfaces {
et-0/0/0 {
description "More Bandwidth!";
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
}
```
#### jnprsr-subtree
is an interactive CLI allowing you to navigate a configuration (almost) as if you are working on a real device.
Once you have loaded the configuration from a file, you can use the auto-completion function using the `<TAB>` key. You can navigate to a suggestion using the arrow keys.
This script can be helpful when navigating large configuration files.
#### jnprsr-merge
allow you to merge a given configuration onto another configuration. It behaves like a `load merge` operation on an existing configuration.
```
$ cat test1.txt
system {
host-name "test";
}
$ cat test2.txt
system {
name-server {
10.4.3.222;
}
}
$ jnprsr-merge test1.txt test2.txt
system {
host-name "test";
name-server {
10.4.3.222;
}
}
```
### In your python script
You can easily use **jnprsr** in your own scripts. For this you will almost always start with the `get_ast()` function. It will parse a given string and return an object of the type `JuniperASTNode`. This datatype inherits properties from the anytree `NodeMixin` type. So you can work with this object the same way you would work with an anytree tree.
For ease of use we have created some helper functions that allow
```
import jnprsr
config = "system { host-name "test"; }"
ast = jnprsr.get_ast(config)
```
For ease of use we have created some Juniper Configuration specific helper functions:
- `render_config_from_ast(ast: JuniperASTNode) -> str`
- This will return a textual representation of the AST, meaning it will converted back into configuration text.
- `render_ascii_tree_from_ast(ast: JuniperASTNode) -> str`
- This will return an ascii tree representing the AST, because why not? :)
- `render_dict_from_ast(ast: JuniperASTNode) -> dict`
- This will return a dictionary from a given configuration file.
- `merge(ast1, ast2) -> JuniperASTNode`
- This will merge ast2 onto ast1
- `get_sub_tree(ast: JuniperASTNode, path: str) -> JuniperASTNode`
- This will return the subtree at specified path, for example 'interfaces et-0/0/0'
Raw data
{
"_id": null,
"home_page": null,
"name": "jnprsr",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": "markusju <markus.jungbluth@gmail.com>",
"keywords": "jnpr, juniper, parser, junos, configuration, config",
"author": null,
"author_email": "markusju <markus.jungbluth@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/89/cd/048a0a33733c7b6e77dd28eaa7202d768a4fb99e353e51507666304d9013/jnprsr-0.1.1.tar.gz",
"platform": null,
"description": "# jnprsr \n\n\njnprsr ('\u02a4un\u0259p\u0251rs\u0259r) is a **Parser** for **Juniper configuration files**.\n\nIt is based around a Lexer and Parser built using **ANTLR4** (https://www.antlr.org/). The formal grammar used in our project was initially created by the **batfish** (https://github.com/batfish/batfish) project.\n\nOur tool allows to generate an **Abstract Syntax Tree (AST)** from a given Juniper configuration file.\nThis **AST** can then be processed further. Currently, we provide the following functions:\n\n* **Pretty-Printing**\n* **Configuration Merge**\n* **Sub-Tree Selection**\n\n\nThe **AST** generated by our implementation uses a data-type provided by the **anytree** (https://github.com/c0fec0de/anytree) library. You can easily process the **AST** generated by our implementation and use it in our own tools.\n\n*Please note: This is currently still a **beta release**. This product comes with absolutely no warranty. It is neither supported nor endorsed in any way by Juniper Networks Inc. We assume no liability for any undesired or incorrect behavior you might experience with this software. If you break your network using **jnprsr**, it is your responsibility and you should be ashamed of yourself for not testing your software properly.*\n\n## Installation\n\nYou can install jnprsr using pip:\n```\npip install jnprsr\n```\n\nYou can also install directly from Git:\n```\npip install git+https://github.com/markusju/jnprsr.git\n```\n## TL;DR - What you can do with jnprsr\n\n### Pretty-Printing\nIt allows you to transform a configuration file looking like this\n\n```\ninterfaces { et-0/0/0 {description \"More Bandwidth!\"; unit 0 {family inet{address 192.0.2.1/24;}}}}\n```\n\ninto this\n\n```\ninterfaces {\n et-0/0/0 {\n description \"More Bandwidth!\";\n unit 0 {\n family inet {\n address 192.0.2.1/24;\n }\n }\n }\n}\n```\n\n### Configuration Merge\n\nSuppose you have this snippet\n```\ninterfaces {\n et-0/0/0 {\n description \"Skynet NNI\";\n }\n}\n```\n\nand this target configuration\n```\ninterfaces {\n et-0/0/0 {\n unit 0 {\n family inet {\n address 192.0.2.1/24;\n } \n }\n }\n}\n```\n\nusing **jnprsr** you can perform a `> load merge` operation on the target configuration with the snippet to generate this:\n\n``` \ninterfaces {\n et-0/0/0 {\n description \"Skynet NNI\";\n unit 0 {\n family inet {\n address 192.0.2.1/24;\n } \n }\n }\n}\n```\n\n\n### Sub-Tree Selection\n\nLet's say you have this configuration file:\n```\nprotocols {\n bgp {\n group SKYNET-PEER {\n type external;\n peer-as 1337;\n neighbor 1.2.3.4;\n }\n group EVILCORP-PEER {\n type external;\n peer-as 1338;\n neighbor 1.2.3.5;\n }\n group UMBRELLACORP-PEER {\n type external;\n peer-as 1339;\n neighbor 1.2.3.6;\n }\n }\n}\n```\n\nand you want to access the sub-tree of the *SKYNET-PEER* BGP peer-group. \n\nUsing **jnprsr** you can easily perform the equivalent of\n`> show configuration protocols bgp group SKYNET-PEER`:\n\n```\nprotocols {\n bgp {\n group SKYNET-PEER {\n type external;\n peer-as 1337;\n neighbor 1.2.3.4;\n }\n }\n}\n```\n\n### Other Stuff\n\nSince **jnprsr** creates an anytree object, you can easily work with the parsed configuration data. \nSome things you could do include, but are not limited to:\n\n* Validation and/or Verification: Does a certain configuration element or sub-tree exist?\n* Comparison: Comparing two given configurations, what nodes are different?\n* Editing: Create, Remove, Change a given configuration and generate textual output from the changed tree again.\n\n\n## Getting Started\n\n### On the shell\n\n**jnprsr** currently comes with 3 commands that you can use on your shell:\n- jnprsr-pretty\n- jnprsr-subtree\n- jnprsr-merge\n\n#### jnprsr-pretty\nis a pretty printer. You can supply a Juniper Configuration file and it will [*pretty print*](https://en.wikipedia.org/wiki/Prettyprint) the received configuration. Meaning that the configuration is returned with the proper indentation and spacing.\nYou can use the script interactively. Simply call it and then paste the configuration. You can end your input on an empty new line with `CTRL+D` or by typing `!END`.\n\n```\n$ jnprsr-pretty\n[Type CTRL+D or '!END' at a new line to end input]\ninterfaces { et-0/0/0 {description \"More Bandwidth!\"; unit 0 {family inet{address 192.0.2.1/24;}}}}\ninterfaces {\n et-0/0/0 {\n description \"More Bandwidth!\";\n unit 0 {\n family inet {\n address 192.0.2.1/24;\n }\n }\n }\n}\n```\n\nAlternatively you can also simply pipe your messed up config at the script to make it pretty. In this case you do not need to end the input.\nNote that we are using the `-s` flag in this example. This silences any additional output, so that you can process the output more easily.\n\n```\n$ cat what-a-mess.txt | jnprsr-pretty -s\ninterfaces {\n et-0/0/0 {\n description \"More Bandwidth!\";\n unit 0 {\n family inet {\n address 192.0.2.1/24;\n }\n }\n }\n}\n```\n\n#### jnprsr-subtree\n\nis an interactive CLI allowing you to navigate a configuration (almost) as if you are working on a real device.\nOnce you have loaded the configuration from a file, you can use the auto-completion function using the `<TAB>` key. You can navigate to a suggestion using the arrow keys.\nThis script can be helpful when navigating large configuration files.\n\n\n\n#### jnprsr-merge\n\nallow you to merge a given configuration onto another configuration. It behaves like a `load merge` operation on an existing configuration.\n\n```\n$ cat test1.txt\nsystem {\n host-name \"test\";\n}\n$ cat test2.txt\nsystem {\n name-server {\n 10.4.3.222;\n }\n}\n$ jnprsr-merge test1.txt test2.txt\nsystem {\n host-name \"test\";\n name-server {\n 10.4.3.222;\n }\n}\n```\n\n### In your python script\n\nYou can easily use **jnprsr** in your own scripts. For this you will almost always start with the `get_ast()` function. It will parse a given string and return an object of the type `JuniperASTNode`. This datatype inherits properties from the anytree `NodeMixin` type. So you can work with this object the same way you would work with an anytree tree.\nFor ease of use we have created some helper functions that allow \n\n```\nimport jnprsr\n\nconfig = \"system { host-name \"test\"; }\"\nast = jnprsr.get_ast(config)\n```\n\nFor ease of use we have created some Juniper Configuration specific helper functions:\n\n- `render_config_from_ast(ast: JuniperASTNode) -> str`\n - This will return a textual representation of the AST, meaning it will converted back into configuration text.\n- `render_ascii_tree_from_ast(ast: JuniperASTNode) -> str`\n - This will return an ascii tree representing the AST, because why not? :)\n- `render_dict_from_ast(ast: JuniperASTNode) -> dict`\n - This will return a dictionary from a given configuration file.\n- `merge(ast1, ast2) -> JuniperASTNode`\n - This will merge ast2 onto ast1\n- `get_sub_tree(ast: JuniperASTNode, path: str) -> JuniperASTNode`\n - This will return the subtree at specified path, for example 'interfaces et-0/0/0'\n",
"bugtrack_url": null,
"license": "Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n \n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n \n 1. Definitions.\n \n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n \n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n \n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n \n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n \n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n \n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n \n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n \n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n \n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n \n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n \n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n \n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n \n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n \n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n \n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n \n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n \n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n \n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n \n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n \n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n \n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n \n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n \n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n \n END OF TERMS AND CONDITIONS\n \n APPENDIX: How to apply the Apache License to your work.\n \n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n \n Copyright [yyyy] [name of copyright owner]\n \n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n \n http://www.apache.org/licenses/LICENSE-2.0\n \n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n ",
"summary": "jnprsr is a Parser for Juniper Configuration Files",
"version": "0.1.1",
"project_urls": {
"Bug Reports": "https://github.com/markusju/jnprsr/issues",
"Homepage": "https://github.com/markusju/jnprsr/",
"Source": "https://github.com/markusju/jnprsr/"
},
"split_keywords": [
"jnpr",
" juniper",
" parser",
" junos",
" configuration",
" config"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "1570cf98ef1638f8d4d7a70601449d6116b1b9056015d2ded1caeecdc1e0f8b8",
"md5": "5840332610a59a4fe2a8c5c941bb6fff",
"sha256": "c223fe16d411b4f3b4f25e7615dbdea6ddd293808dd0b7e844608b1ed13e3b52"
},
"downloads": -1,
"filename": "jnprsr-0.1.1-py3-none-any.whl",
"has_sig": false,
"md5_digest": "5840332610a59a4fe2a8c5c941bb6fff",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 27566,
"upload_time": "2025-02-12T15:38:50",
"upload_time_iso_8601": "2025-02-12T15:38:50.353034Z",
"url": "https://files.pythonhosted.org/packages/15/70/cf98ef1638f8d4d7a70601449d6116b1b9056015d2ded1caeecdc1e0f8b8/jnprsr-0.1.1-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "89cd048a0a33733c7b6e77dd28eaa7202d768a4fb99e353e51507666304d9013",
"md5": "c46dc2c3ea83b5174f5d651f05776c9b",
"sha256": "7b5d2eba9db7fd2476862f5e937ed719099d976b69cc7cec75f3e25cb0ea0ba5"
},
"downloads": -1,
"filename": "jnprsr-0.1.1.tar.gz",
"has_sig": false,
"md5_digest": "c46dc2c3ea83b5174f5d651f05776c9b",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 29844,
"upload_time": "2025-02-12T15:38:52",
"upload_time_iso_8601": "2025-02-12T15:38:52.483885Z",
"url": "https://files.pythonhosted.org/packages/89/cd/048a0a33733c7b6e77dd28eaa7202d768a4fb99e353e51507666304d9013/jnprsr-0.1.1.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-12 15:38:52",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "markusju",
"github_project": "jnprsr",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"lcname": "jnprsr"
}
