= Adobe Creative Cloud Updates =

== aamporter setup ==
The updates to Creative Cloud apps are imported into the Orchard munki repository from the autopkg build host using Tim Suttons tool [[https://github.com/timsutton/aamporter|aamporter]]. Currently there is a folder named `/srv/munki/aamporter` on stelmaria.oucs.ox.ac.uk which contains:
 * the aamporter script (the folder is a git clone of the Github repo so can `git pull` if it is updated.
 * a number of plists that were generated by running `aamporter.py --build-product-plist [path/to/CCP/pkg/file.ccp] [--munki-update-for BaseProductPkginfoName]` on each of the CC apps generated with Creative Cloud Packager.
 * a plist for aamporter itself which contains the following settings:
{{{#!highlight xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>munkiimport_options</key>
	<array>
		<string>--catalog=testing</string>
	</array>
	<key>munki_repo_destination_path</key>
	<string>Adobe_CC_2015/Updates</string>
</dict>
</plist>
}}}

== Importing into munki ==
Run the shell script (important: as the autopkg user!) `sudo -u autopkg -i /srv/munki/orchard_repo/autoaamporter.sh` (this is not part of aamporter but is a wrapper to automate it) which does the following:
{{{#!highlight bash
#!/bin/bash

ls -G /srv/munki/aamporter/Adobe* | xargs /srv/munki/aamporter/aamporter.py --munkiimport --make-catalogs
}}}
This will send each product plist to aamporter where it will figure out which updates need downloading, download them if they are not cached and then import them into munki according to `aamporter.plist` (therefore into the testing catalog), and finally running makecatalogs.