-
Notifications
You must be signed in to change notification settings - Fork 38
Extension Attributes
Extension attributes work just like scripts. You need a complete and valid XML file for the extension attribute (although it will do variable substitution). To experiment with XML for these, again, use the API page to look through the ones on your JSS. Included with this project there is a template for extension attributes as well, although you will need to edit it to add in your script. As the extension attribute is XML, you will need to properly HTML encode reserved characters; e.g. '<' becomes '<', '>' becomes '%gt;'. Since the extension attributes value needs to be Your Result sent to stdout, you will need to do this manually for every extension attribute.
Solutions to handle this automatically are being considered, but at this moment, XML is not valid if there are < and > sitting around that aren't escaped.
The extension_attributes
input variable should contain an array of dictionaries. Each dictionary should contain an ext_attribute_path
item which is a path to the extension attribute file. You may also skip this key entirely if you don't need extension attributes for your recipe.
Other questions not addressed here? Join us in the #jss-importer channel on the Mac Admins Slack.