ruby-jss 0.11.0a5 → 0.11.0a6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 9c9db6dbef7526403d486b5e511d1a78a6d1e459
-  data.tar.gz: 6f5672d8d22feda70b4c9a7684ca73b2e64bdcaa
+  metadata.gz: 738e376502016631097bea927398750c1606a6f4
+  data.tar.gz: 9a82556c928e8cca44b4e37cd663b5959f9c774b
 SHA512:
-  metadata.gz: 40e09669cd064fa1091f9d44506cd04454fdead9c4e8974bccaa1d123d8d7659cbb976a6c3c0edaf5e40f397d7b637621ed134c9081837ff6bccce5842ca5612
-  data.tar.gz: bac295fbc3b82175c1ddc1c54b4df73e1f8c2285ea21997910f0550e33a9687994d3c2bfce59a35986c2d59df63252fa69f497502b058fab6d02b33303acbcd5
+  metadata.gz: 4b309bc27a8314a2b588678d056760acfcf68abc9b75c4044c0c53c669a57b9b20750acce2a5837dc37d838a9a3b6f28ed8966018a8df48394e5245672a2166f
+  data.tar.gz: 0d5ba01aef444d7e3a24a877b6a9de341a01fce551f9362f850de49bf5a8e2691af8e610e9ae82b14be30e59c2112a882ba432b51fd19b8e94a1d70544650049

data/CHANGES.md

@@ -1,8 +1,6 @@
 # Change History
 
-## v 0.11.0a5 2018-02-15
-
-- Fix: Updating JSS::Extendable objects with no changes to ext. attribs will no longer erase all ext attrib values. (!)
+## v 0.11.0, 2018-02-19
 
 - Improvement: Updated general attributes for computers and mobile devices
 
@@ -22,19 +20,23 @@
 
 - Fix: Scope objects use the api connection of their container
 
+- Improvement: 'devmode', use `JSS.devmode \[:on|:off]`` to set, and `JSS.devmode?`` to query.  Useful for developers, esp. in `irb` who want, e.g. to have a method output some state when in devmode, instead of/as well as behaving normally. This is currently the case for `JSS::MDM.send_mdm_command`.  When devmode? is true, the XML sent to the API for the command is printed to stdout before the command is sent to the target machine.
+
 - Improvement: Computer app usage & mgmt data methods are now class methods, so can be used without instantiating the computer.
   The instance methods remain, and they now just use the class methods.
 
-- Improvement/Change: All handling of management history for Computers and MobileDevices is in the new ManagementHistory module.
+- Improvement/Change: All handling of management history for Computers and MobileDevices is in the new ManagementHistory module. The module
+  is mixed into JSS::Computer and JSS::MobileDevice, so its methods are available to those classes and their instances. Note that some
+  history events are only available in Computers or MobileDevices, and some are available in both.
 
   The primary query method (.management_history) returns the raw JSON data from the API, possibly for a subset of the data, as a Ruby Hash
-  with symbolized keys. This data is somewhat inconsistent in it's structure and content across the different types of history events,
+  with symbolized keys. This data is somewhat inconsistent in its structure and content across the different types of history events,
   but you're welcome to use it if needed.
 
   All other methods now return Arrays of various instances of classes defined in the module.
 
-  For example, the {JSS::ManagementHistory.audit_history} method returns an Array of JSS::ManagementHistory::AuditEvent instances,  and the
-  {JSS::ManagementHistory.completed_policies} gives an Array of JSS::ManagementHistory::PolicyLog objects. These objects are read-only and
+  For example, the {JSS::MobileDevice.audit_history} method returns an Array of JSS::ManagementHistory::AuditEvent instances,  and the
+  {JSS::Computer.completed_policies} gives an Array of JSS::ManagementHistory::PolicyLog objects. These objects are read-only and
   provide access to their values via attribute-style methods.
 
   As with MDM command handling, and computer app usage and mgmt data, the work is done by class methods, so that the data is available without creating instances of the Computers or MobileDevices, and the instance methods just
@@ -43,7 +45,11 @@
   *WARNING* these changes mean that the methods returning Arrays of ManagementHistory class instances are not backward compatible,
   since the earlier versions returned Hashes
 
-## v 0.10.1 2017-11-08
+## v 0.10.2, 2018-02-16
+
+-  *IMPORTANT BUG FIX*: Updating JSS::Extendable objects with no changes to ext. attribs will no longer erase all ext attrib values. (!)
+
+## v 0.10.1, 2017-11-08
 
 - Add: Extension Attribute values that are populated by Script or LDAP can now be modified via Extendable#set_ext_attr.
 
@@ -59,7 +65,7 @@
 
 - Fix: A few lingering methods that weren't multi-APIConnection aware, are now aware
 
-## v0.10.0 2017-10-09
+## v0.10.0, 2017-10-09
 
 - Improvement: Working with multiple APIConnections is now far more flexible!
 
@@ -90,7 +96,7 @@
 
 - Add: Computer objects now have a `last_enrolled` attribute
 
-## v0.9.3 2017-08-08
+## v0.9.3, 2017-08-08
 
 - Add: JSS::Computer instance now allow you to modify mac_address, alt_mac_address, udid, and serial_number.
   Note: even tho the WebUI doesn't allow editing of the serial_number, the API does and doing so can be useful
@@ -99,11 +105,11 @@
 - Add: JSS::Validate module, to consoliday generic data-validation methods. Methods will be moved to it from
   other places over time.
 
-## v0.9.2 2017-07-25
+## v0.9.2, 2017-07-25
 
 - Fix: parsing of JSS versions > 9.99
 
-## v0.9.0 2017-07-17
+## v0.9.0, 2017-07-17
 
 - Add: JSS::MobileDevice.all_apple_tvs class method
 - Add: JSS::MobileDevice.management_history method, and related methods in instances
@@ -135,17 +141,17 @@
 - Improvement: JSS::Policy instances can now flush their logs
 - Improvement: JSS::Policy now has setters for server_side_activation and server_side_expriation.
 
-## v0.8.3 2017-06-07
+## v0.8.3, 2017-06-07
 
 - Fix: Version parsing: empty version parts default to 0, e.g. 10.2 parses as 10.2.0
 
-## v0.8.2 2017-06-07
+## v0.8.2, 2017-06-07
 
 - Fix: Some objects failed to locate their 'main subset' (the chunk of API data that contains the object name and id) correctly.
 - Fix: Some versions of Gem::Version don't like dashes (which are part of SemVers).
 
 
-## v0.8.1 2017-06-05
+## v0.8.1, 2017-06-05
 
 - Improvement: Support for the new semantic versioning of Jamf products starting with Jamf Pro 9.99
 - The alpha 'Webhooks framework' has been removed from ruby-jss and will reappear soon as it's own project with a new name.
@@ -153,7 +159,7 @@
 - Improvement: JSS::APIObject and subclasses now have .fetch and .make class methods which are wrappers for .new. .fetch is the preferred way to retrieve instances of existing API objects, and .make for making not-yet-existing objects to be created in the JSS. The .new class method still works as before, but is considered deprecated.
 - Improvement: JSS::APIConnection now has a #rest_url attribute that returns the base of the url for the current REST connection, e.g. "https://jamf.company.com:8443/JSSResource", or nil if not connected.
 
-## v0.8.0 2017-04-07
+## v0.8.0, 2017-04-07
 
 - Change: Lots of code cleanup to follow RuboCop guidelines (more of this comming)
 - Fix: sometimes the port would default to 80 rather than 8443
@@ -173,18 +179,18 @@
 - Add: first attempts at adding SSL/TLS support to the Webhooks framework.
   - NOTE: the Webhooks framework is still 'alpha' code, and will be moved into a separate git repo eventually. It doesn't rely on ruby-jss.
 
-## v0.7.0 2017-02-01
+## v0.7.0, 2017-02-01
 
 - JSS::NetworkSegment - many bugfixes and cleanup. I didn't really have a proper grasp of IP CIDR masks before and how they (don't) relate to the IP ranges used by Network Segments in the JSS. The CIDRs and full netmasks can still be used to set the ending addresses of NetworkSegment objects, but the #cidr method is gone, since it was meaningless for segments that didn't match subnet-ranges.
 - subnect-update, the example command in the bin directory, has been renamed to negseg-update. It's also been cleaned up and uses the new functionality of JSS::NetworkSegment.
 - JSS::DBConnection - fixed a bug where meaningless IO 'stream closed' errors would appear when closing the DB connection.
 
-## v0.6.7 2017-01-03
+## v0.6.7, 2017-01-03
 
 - Added class JSS::WebHook, which requires Jamf Pro 9.97 or higher.
   - NOTE: This is access to the WebHooks themselves as defined in Jamf Pro, and is separate from the  WebHook-handling framework included in the previous release for testing.
 
-## v0.6.6 2016-11-30
+## v0.6.6, 2016-11-30
 
 - Added String#jss_to_pathname to convert Strings to Pathname instances in JSS::Configuration.
 - JSS::DBConnection#connect now returns the server hostname, to match the behavior of JSS::APIConnection#connect
@@ -197,7 +203,7 @@
 - Starting cleaning up code to better adhere to [RuboCop](http://rubocop.readthedocs.io/en/latest/) standards
 - Added alpha version of a JSS WebHooks framwork
 
-## v0.6.5 2016-08-10
+## v0.6.5, 2016-08-10
 
 - Cleanup of redundant constants (Thanks @aurica!)
 - Added JSS::ComputerInvitation class (Thanks @tostart-pickagreatname!)
@@ -206,7 +212,7 @@
 - JSS::Computer: added methods #boot_drive, #filevault2_enabled?, and #filevault1_accounts
 - Various small bugfixes & improvements
 
-## v0.6.4 2016-03-24
+## v0.6.4, 2016-03-24
 
 - JSS::Package#dlete can optionally delete the master file at the same time
 - Added an example ruby-jss.conf file with internal documentation
@@ -214,11 +220,11 @@
 - Updated the config file name to match the new gem name, maintaining backwards compatibility
 - Improved error messages
 
-## v0.6.3 2016-03-09
+## v0.6.3, 2016-03-09
 
 Maintenence version bump to fix an issue uploading to rubygems.org
 
-## v0.6.2 2016-03-08
+## v0.6.2, 2016-03-08
 
 As of v0.6.2, the github project, and rubygem have been renamed to 'ruby-jss'. The 'require' name is now 'jss'.
 
@@ -239,14 +245,14 @@ The 'jss-api' gem has been updated one last time, also to v0.6.2. That gem has a
 - JSS::Composer::mk_dmg fix for building/indexing dmg's, no longer creates an unreadable .Trashes folder.
 - Several small typos and other tiny bugs.
 
-## v0.6.1 2016-03-01
+## v0.6.1, 2016-03-01
 
 #### additions & features
 
 - JSS::Package#install now takes :alt_download_url argument.Can be used to specify a custom URL from which to download a pkg/dmg for installation with 'jamf install'. This allows the use of cloud distribution points.
 - JSS::DistributionPoint: Added reachability methods, improved assessment of mount-success. #reachable_for_download? and #reachable_for_upload? will now return a boolean indicating if the DistPoint is reachable.
 
-## v0.6.0 2016-01-06
+## v0.6.0, 2016-01-06
 
 This version of the jss-api gem incorporates changes needed for the upcoming release of d3 (a.k.a. depot3),
 a package/patch management system for Casper, which was the reason for the jss-api gem to begin with.
@@ -284,7 +290,7 @@ Now the actual install command is examined, and if its exitstatus is zero, Packa
 Also: As of casper 9.72, the argument requirements havechanged for 'jamf install' with http downloads. This is now handled correctly
 
 
-## v0.5.8 2015-09-22
+## v0.5.8, 2015-09-22
 
 #### bugfixes & cleanup
 
@@ -299,7 +305,7 @@ Also: As of casper 9.72, the argument requirements havechanged for 'jamf install
 - TimeoutError and AuthenticationError have been added to exceptions
 - Policy objects now have a #run method - attempts to execute the policy locally.
 
-## v0.5.7 2015-05-26
+## v0.5.7, 2015-05-26
 
 #### bugfixes & cleanup
 
@@ -313,7 +319,7 @@ Also: As of casper 9.72, the argument requirements havechanged for 'jamf install
 - Package#required_processor: remove buggy line of ancient, deprecated code
 - Package#upload_master_file: move autoupdate to appropriate location
 
-## v0.5.6 2014-11-04
+## v0.5.6, 2014-11-04
 
 - now requires Ruby >= 1.9.3 and rest-client >= 1.7.0. Needed for Casper >= 9.61's lack of support for SSLv3.
 - APIConnection now accepts :ssl_version option in the argument hash. Defaults to 'TLSv1'
@@ -322,6 +328,6 @@ Also: As of casper 9.72, the argument requirements havechanged for 'jamf install
 - many documentation updates as we adjust to being live
 - minor bugfixes
 
-## v0.5.0 2014-10-23
+## v0.5.0, 2014-10-23
 
 - first opensource release

data/README.md

@@ -1,4 +1,4 @@
-# ruby-jss: Access to the Jamf Pro from Ruby
+# ruby-jss: Working with the Jamf Pro API in Ruby
 [![Gem Version](https://badge.fury.io/rb/ruby-jss.svg)](http://badge.fury.io/rb/ruby-jss)
 
 ### Table of contents
@@ -29,14 +29,14 @@
 
 The ruby-jss project provides a Ruby module called JSS, which is used for accessing the REST API of
 the JAMF Software Server (JSS), the core of Jamf Pro, an enterprise-level management tool for Apple
-devices from [JAMF Software, LLC](http://www.jamf.com/). It is available as a
+devices from [Jamf.com](http://www.jamf.com/). It is available as a
 [rubygem](https://rubygems.org/gems/ruby-jss), and the
 [source is on github](https://github.com/PixarAnimationStudios/ruby-jss).
 
 The module abstracts API resources as Ruby objects, and provides methods for interacting with those
 resources. It also provides some features that aren't a part of the API itself, but come with other
 Jamf-related tools, such as uploading .pkg and .dmg {JSS::Package} data to the master distribution
-point, and the installation of {JSS::Package} objects on client machines. (See [BEYOND THE API](#beyond-the-api)
+point, and the installation of {JSS::Package} objects on client machines. (See [BEYOND THE API](#beyond-the-api))
 
 The module is not a complete implementation of the Jamf API. Only some API objects are modeled, some
 only minimally. Of those, some are read-only, some partially writable, some fully read-write (all
@@ -50,6 +50,8 @@ Hopefully others will find it useful, and add more to it as well.
 
 ## SYNOPSIS
 
+Here are some simple examples of using ruby-jss
+
 ```ruby
 require 'ruby-jss'
 
@@ -100,13 +102,13 @@ Before you can work with JSS Objects via the API, you have to connect to it.
 
 The method `JSS.api` retruns the currently active connection to the API (an instance of a {JSS::APIConnection}, q.v.).
 
-When the JSS Module is first loaded, that connection isn't connected. To remedy that, use JSS.api.connect, passing it values for the connection. In this example, those values are stored in the local variables jss_user, jss_user_pw, and jss_server_hostname, and others are left as default.
+When the JSS Module is first loaded, that connection object isn't connected to anything. To remedy that, use `JSS.api.connect`, passing it values for the connection. In this example, those values are stored in the local variables jss_user, jss_user_pw, and jss_server_hostname, and others are left as default.
 
 ```ruby
 JSS.api.connect user: jss_user, pw: jss_user_pw, server: jss_server_hostname
 ```
 
-Make sure the user has privileges in the JSS to do things with desired Objects. Note that these might be more than you think, since some objects refer to other objects, like Sites and Categories.
+Make sure the user has privileges in the JSS to do things with desired objects. Note that these might be more than you think, since some objects refer to other objects, like Sites and Categories.
 
 If the server name given ends with 'jamfcloud.com' the port number will default to 443 via SSL.  Otherwise, it defaults to 8443 with SSL (the default port for locally-hosted servers). In other situations, you can specify it with the `port:` and `use_ssl:` parameters.
 
@@ -118,7 +120,7 @@ server connection parameters in a simple config file.
 
 ### Working with JSS Objects (a.k.a REST Resources)
 
-All API Object classes are subclasses of JSS::APIObject and share methods for listing, retrieving, and deleting from the JSS. All supported objects can be listed, retrieved and deleted, but only some can be updated or created. See below for the level of implementation of each class.
+All of the ruby classes representing objects in Jamf Pro are subclasse of, or modules within, JSS::APIObject and share methods for creating, listing, retrieving, updating, and deleting via the API. All supported objects can be listed, retrieved and deleted, but only some can be updated or created. See below for the level of implementation of each class.
 
 --------
 
@@ -138,14 +140,13 @@ JSS::Computer.all_names # =>  ["cephei", "peterparker", "rowdy", ...]
 JSS::Computer.all_ids # =>  [1122, 1218, 931, ...]
 ```
 
-Some Classes provide other ways to list objects, depending on the data available, e.g. JSS::MobileDevice.all\_udids
+Some Classes provide other ways to list objects, depending on the data available, e.g. JSS::MobileDevice.all\_udids or JSS::Computer.all\_laptops
 
 --------
 
 #### Retrieving Objects
 
-To retrieve a single object call the class's .fetch method and provide a name:,  id:, or other valid
-lookup attribute.
+To retrieve a single object call the class's `.fetch` method and provide a name:,  id:, or other valid identfier.
 
 
 ```ruby
@@ -154,14 +155,16 @@ a_dept = JSS::Department.fetch name: 'Payroll'# =>  #<JSS::Department:0x10b4c081
 
 Some classes can use more than just the :id and :name keys for lookups, e.g. computers can be looked up with :udid, :serial_number, or :mac_address.
 
-*NOTE*: A class's '.fetch' method is now the preferred method to use for retrieving existing objects. The '.new' method still works as before, but is
-deprecated for object retrieval and doing so may raise errors in the future. See below for using .make to create new objects in the JSS.
+You can even fetch objects without specifying the kind of identifier, e.g. `JSS::Computer.fetch 3241`, but this will be slower, since ruby-jss searches by matching the given value with all available identifiers, returning the first match.
+
+*NOTE*: A class's '.fetch' method is now the preferred method to use for retrieving existing objects.
+The '.new' method still works as before, but is deprecated for object retrieval and doing so may raise errors in the future. See below for using .make to create new objects in the JSS.
 
 --------
 
 #### Creating Objects
 
-Some Objects can be created anew in the JSS via ruby. To do so, first make a Ruby object using the class's .make method and providinga unique :name:, e.g.
+Some Objects can be created anew in the JSS via ruby. To do so, first make a Ruby object using the class's `.make` method and providing a unique :name:, e.g.
 
 ```ruby
 new_pkg = JSS::Package.make name: "transmogrifier-2.3-1.pkg"
@@ -217,13 +220,15 @@ To delete an object without fetching it, use the class's .delete method and prov
 JSS::Script.delete [321, 543, 374]
 ```
 
-See JSS::APIObject, the parent class of all API resources, for general information about creating, reading, updating/saving, and deleting resources.
+See [JSS::APIObject](http://www.rubydoc.info/gems/ruby-jss/JSS/APIObject), the parent class of all API resources, for general information about creating, reading, updating/saving, and deleting resources.
 
 See the individual subclasses for any details specific to them.
 
 ## OBJECTS IMPLEMENTED
 
-See each Class's documentation for details.
+While the API itself supports nearly full CRUD (Create,Read,Update,Delete) for all objects, ruby-jss doesn't yet do so. Why? Because implementing the data validation and other parts needed for creating & updating can be time-consuming and we've focused on what we needed. As we keep developing ruby-jss, this list changes. If you'd like to help implement some of these objects more fully, please fork the github project and reach out to us at ruby-jss@pixar.com.
+
+Here's what we've implemented so far. See each Class's [documentation(http://www.rubydoc.info/gems/ruby-jss)] for details.
 
 ### Creatable and Updatable
 
@@ -250,34 +255,15 @@ See each Class's documentation for details.
 * {JSS::UserExtensionAttribute}
 * {JSS::UserGroup}
 * {JSS::WebHook}
+* {JSS::Computer}
+* {JSS::MobileDevice}
+* {JSS::Policy} (still not fully implemented)
 
-### Updatable but not Creatable
-
-* {JSS::Computer} - limited to modifying
-  * name
-  * barcodes
-  * asset tag
-  * ip address
-  * location data
-  * purchasing data
-  * editable extension attributes
-* {JSS::MobileDevice} - limited to modifying
-  * asset tag
-  * location data
-  * purchasing data
-  * editable extension attributes
-* {JSS::Policy} - limited  to modifying
-  * scope (see {JSS::Scopable::Scope})
-  * name
-  * enabled
-  * category
-  * triggers
-  * packages
-  * scripts
-  * file & process actions
-* {JSS::OSXConfigurationProfile}
+**NOTE** Computer and Mobile Device data gathered by an Inventory Upate (a.k.a. 'recon') is not editable.
 
-**NOTE** Even in the API and the WebApp, Computer and Mobile Device data gathered by an Inventory Upate (a.k.a. 'recon') is not editable.
+### Updatable, but must be created in the Web UI
+
+* {JSS::OSXConfigurationProfile}
 
 ### Creatable only
 
@@ -296,19 +282,21 @@ These must be created and edited via the JSS WebApp
 
 All supported API Objects can be deleted
 
-Other useful classes:
+Other useful classes & modules:
 
 * {JSS::APIConnection} - An object representing the connection to the REST API
-* {JSS::DBConnection} - An object representing the connection to MySQL database, if used
+* {JSS::DBConnection} - An object representing the connection to MySQL database, if used.
 * {JSS::Server} - An encapsulation of some info about the JamfPro server, such as the version and license. An instance is available as an attribute of the {JSS::APIConnection} singleton.
 * {JSS::Client} - An object representing the local machine as a Casper-managed client, and JAMF-related info and methods
-
+* {JSS::ManagementHistory} - a module for handing the management history for Computers and Mobile Devices. It defines many read-only classes representing events in a machine's history.
+* {JSS::Scopable} - a module that handles Scope for those objects that can be scoped. It defines the Scope class used in those objects.
+* {JSS::MDM} - a module that handles sending MDM commands to Computers and Mobile Devices
 
 ## CONFIGURATION
 
-The {JSS::Configuration} singleton class is used to read, write, and use site-specific defaults for the JSS module. When the Module is required, the single instance of {JSS::Configuration} is created and stored in the constant {JSS::CONFIG}. At that time the system-wide file /etc/jss_gem.conf is examined if it exists, and the items in it are loaded into the attributes of {JSS::CONFIG}. The user-specific file ~/.jss_gem.conf then is examined if it exists, and any items defined there will override those values from the system-wide file.
+The {JSS::Configuration} singleton class is used to read, write, and use site-specific defaults for the JSS module. When ruby-jss is required, the single instance of {JSS::Configuration} is created and stored in the constant {JSS::CONFIG}. At that time the system-wide file /etc/ruby-jss.conf is examined if it exists, and the items in it are loaded into the attributes of {JSS::CONFIG}. The user-specific file ~/.ruby-hss.conf then is examined if it exists, and any items defined there will override those values from the system-wide file.
 
-The values defined in those files are used as defaults throughout the module. Currently, those values are only related to establishing the API connection. For example, if a server name is defined, then a :server does not have to be specified when calling {JSS::API#connect}. Values provided explicitly when calling JSS.api.connect will override the config values.
+The values defined in those files are used as defaults throughout the module. Currently, those values are only related to establishing the API connection. For example, if a server name is defined, then a :server does not have to be specified when calling {JSS::APIConnection#connect}. Values provided explicitly when calling JSS::APIConnection#connect will override the config values.
 
 While the {JSS::Configuration} class provides methods for changing the values, saving the files, and re-reading them, or reading an arbitrary file, the files are text files with a simple format, and can be created by any means desired. The file format is one attribute per line, thus:
 
@@ -325,7 +313,7 @@ The currently known attributes are:
 * api_timeout_open [Integer] the number of seconds for the open-connection timeout
 * api_timeout [Integer] the number of seconds for the response timeout
 
-To put a standard server & username on all client machines, and auto-accept the JSS's self-signed https certificate, create the file /etc/jss_gem.conf containing three lines like this:
+To put a standard server & username on all client machines, and auto-accept the JSS's self-signed https certificate, create the file /etc/ruby-jss.conf containing three lines like this:
 
 ```
 api_server_name: casper.myschool.edu
@@ -413,13 +401,13 @@ In general, you can install ruby-jss with this command:
 
 Full documentation is available at [rubydoc.info](http://www.rubydoc.info/gems/ruby-jss/)
 
-[Email the developer](mailto:ruby-jss@pixar.com)
+[Email the developers](mailto:ruby-jss@pixar.com)
 
 [Macadmins Slack Channel](https://macadmins.slack.com/messages/#jss-api/)
 
 ## LICENSE
 
-Copyright 2017 Pixar
+Copyright 2018 Pixar
 
 Licensed under the Apache License, Version 2.0 (the "Apache License") with
 modifications. See LICENSE.txt for details

data/bin/cgrouper

@@ -1,6 +1,6 @@
 #!/usr/bin/ruby
 
-### Copyright 2017 Pixar
+### Copyright 2018 Pixar
 
 ###
 ###    Licensed under the Apache License, Version 2.0 (the "Apache License")

data/bin/jamfHelperBackgrounder

@@ -1,6 +1,6 @@
 #!/usr/bin/ruby
 
-### Copyright 2017 Pixar
+### Copyright 2018 Pixar
 
 ###
 ###    Licensed under the Apache License, Version 2.0 (the "Apache License")

data/bin/netseg-update

@@ -1,6 +1,6 @@
 #!/usr/bin/ruby
 
-### Copyright 2017 Pixar
+### Copyright 2018 Pixar
 
 ###
 ###    Licensed under the Apache License, Version 2.0 (the "Apache License")