puppet-pson 1.1.10

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: bb042b282fec5f28bd294898b6b435064301a165a9af99e71a3332d0be0e866b
+  data.tar.gz: 8420168506ed72a4b1ba023f87709e469fd6135b6adff3e492414b2601fd2c92
+SHA512:
+  metadata.gz: a35a90d4a0dacefe172b18808f448090e1eeb76a38483e171b1d70469610ab38243c591a709d66a40bf2af18374a13e2398546a0d9fcb540a486a73c9be238be
+  data.tar.gz: e270512fedba002f929e05125f3b754c15cb43613ab8dfd73914a0cdfd66ce81508c59bc2a0451b4499f8cc030e5360ec728d642990a866c8ea3208afedf6d9c

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/CODEOWNERS

@@ -0,0 +1,2 @@
+# added by slack-gitbot
+* @puppetlabs/phoenix

data/Gemfile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in puppet-pson.gemspec
+gemspec
+
+gem "rake", "~> 13.0"
+
+gem "rspec", "~> 3.0"

data/LICENSE.txt

@@ -0,0 +1,201 @@
+                                 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.

data/README.md

@@ -0,0 +1,116 @@
+PSON
+=============
+
+PSON is a variant of [JSON](http://json.org) that puppet uses for serializing
+data to transmit across the network or store on disk. Whereas JSON requires
+that the serialized form is valid unicode (usually UTF-8), PSON is 8-bit ASCII,
+which allows it to represent arbitrary byte sequences in strings.
+
+PSON was forked from upstream [pure JSON v1.1.9](https://github.com/flori/json/tree/v1.1.9/lib/json/pure) and patches
+were added to [allow binary data](https://github.com/puppetlabs/puppet/commit/3c56705a95c945778674f9792a07b66b879cb48e).
+
+Puppet uses the MIME types "pson" and "text/pson" to refer to PSON.
+
+JSON Strings
+-------------
+
+A JSON string is encoded in Unicode. The string must start and end with " (ASCII
+0x22). Between these characters, double quote, reverse solidus (backslash) and
+control characters (\u0000 - \u001F) must be escaped, all others may be escaped.
+
+The escape process replaces each code point with "reverse solidus, followed by
+the lowercase letter u, followed by four hexadecimal digits that encode the
+character's code point." For example, the ASCII record separator character
+(\u001F) is serialized in JSON as:
+
+    0x5C 0x75 0x30 0x30 0x31 0x45
+
+In addition, the double quote, reverse solidus and some printable control
+characters are commonly escaped using a shorter form, using a single reverse
+solidus:
+
+    | Byte | ASCII Character | Encoded Sequence | Encoded ASCII Sequence |
+    | ---- | --------------- | ---------------- | ---------------------- |
+    | 0x22 | "               | 0x5C, 0x22       | \"                     |
+    | 0x5c | \               | 0x5C, 0x5C       | \\                     |
+    | 0x08 | Backspace       | 0x5C, 0x62       | \b                     |
+    | 0x09 | Horizontal Tab  | 0x5C, 0x74       | \t                     |
+    | 0x0A | Line Feed       | 0x5C, 0x6E       | \n                     |
+    | 0x0C | Form Feed       | 0x5C, 0x66       | \f                     |
+    | 0x0D | Carriage Return | 0x5C, 0x72       | \r                     |
+
+UTF-8/16/32 encodings define a set of rules for how code points are encoded as
+bytes. However, there are some byte sequences that are not a valid encoding for
+any code point. For example, in UTF-8, 0x80 is used to indicate a two byte
+sequence, so the following fails:
+
+    JSON.generate("\x80")
+    #=> JSON::GeneratorError (source sequence is illegal/malformed utf-8)
+
+Differences from JSON
+---------------------
+
+PSON does *not differ* from JSON in its representation of objects, arrays,
+numbers, booleans, and null values. PSON *does* serialize strings differently
+from JSON.
+
+PSON shares the same encoding process as JSON, except that a PSON string is a
+sequence of 8-bit ASCII values. So the string containing 0x80 can be serialized
+*unescaped* as PSON:
+
+    PSON.generate("\x80").bytes.to_a.map { |b| b.to_s(16) }
+    #=> ["22", "80", "22"]
+
+One other difference is that PSON *may* produce strings with 8-bit ASCII
+encoding, unlike JSON:
+
+    PSON.generate("\u20AC").encoding
+    #=> #<Encoding:ASCII-8BIT>
+    JSON.generate("\u20AC").encoding
+    #=> #<Encoding:UTF-8>
+
+Finally, PSON does not roundtrip values that are not arrays or hashes in the same way as JSON:
+
+    JSON.parse(JSON.generate("\x1E"))
+    #=> "\u001E"
+    PSON.parse(PSON.generate("\x1E"))
+    #=> PSON::ParserError (source '"\u001e"' not in PSON!)
+
+whereas PSON can roundtrip an array (or hash) containing that value:
+
+    PSON.parse(PSON.generate(["\x1E"]))
+    #=> ["\u001E"]
+
+Decoding PSON Using JSON Parsers
+--------------------------------
+
+Many languages have JSON parsers already, which can often be used to parse PSON
+data. Although JSON requires that it is encoded as unicode most parsers will
+produce usable output from PSON if they are instructed to interpret the input
+as Latin-1 encoding.
+
+In all these examples there is a file available called `data.pson` that
+contains the ruby structure `{ "data" => "\x07\x08\xC3\xC3" }` encoded as
+PSON (the value is an invalid unicode sequence). In bytes the data is:
+
+    0x7b 0x22 0x64 0x61 0x74 0x61 0x22 0x3a 0x22 0x5c 0x75 0x30 0x30 0x30 0x37 0x5c 0x62 0xc3 0xc3 0x22 0x7d
+
+which represents:
+
+     {    "    d    a    t    a    "   <sp>  "    \    u    0    0    0    7    \    b    0xc3 0xc3 "    }
+
+Python Example:
+
+    >>> import json
+    >>> json.load(open("data.pson"), "latin_1")
+    {u'data': u'\x07\x08\xc3\xc3'}
+
+Clojure Example:
+
+    user> (parse-string (slurp "data.pson" :encoding "ISO-8859-1"))
+    {"data" "^G\bÃÃ"}
+
+Ruby Example:
+
+    irb> JSON.parse(File.read('data.pson', encoding: "ISO-8859-1"))
+    => {"data"=>"\a\bÃÃ"}

data/Rakefile

@@ -0,0 +1,8 @@
+# frozen_string_literal: true
+
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task default: :spec