Package: click-toolbelt
Available commandsLoginUploading a click package requires the developer to submit
an oauth signed request. For this, click-toolbelt needs to first
obtain an oauth token. In order to do so, the user can run the
following (note: be sure to prepend the command with a space so that
your command history doesn’t save the sensitive command).$   click-toolbelt login <email> <password> [otp]On successful execution this command will store the oauth credentials
in$HOME/.config/click-toolbelt/click.cfgand will use it during the
upload step.UploadOnce the user is successfully logged in, he can then upload
the click package. In order to do so, the user can run$ click-toolbelt upload <binary_file> [--metadata <metadata_file>]For this command to be successful, certain criteria must be met:user must be logged in already (seeLogin)the binary file must be a valid click packageuser owns the application for which he’s uploading the click package (if the application already exists)Themetadata_fileparameter should refer to a file containing a json document. If this file is provided,
it will be used to extract extra information not provided in the click package’s manifest.When uploading the initial package, the following fields might be extracted from themetadata_file:tagline: A one line summary for the appdepartment: The app’s category name (seeDepartment)channel: The upload target channel name (seeChannel). If omitted, ‘stable’ is assumed.support_url: A URL users can go to for support for this application. Allows http(s): and mailto: schemeslicense: The license under which the app will be released (seeLicense)icon_256 (or icon): The path to a local file to be uploaded as the icon for the application; the icon must be 256x256 px in sizename: Application name (overrides what’s defined in the click package manifest)description: Application description (overrides what’s defined in the click package manifest)changelog: A description of the changes included since the last uploadscreenshots: A list of paths to local files to be uploaded as screenshots for the applicationblacklist_ids: A list of country codes to prevent the application from being distributed to (seeCountry)whitelist_ids: A list of country codes to limit the application being distributed to (seeCountry)auto_publish: Automatically submit for reviewreviewer_notes: Notes for reviewers to use when reviewing the app’s submissionFor a new version upload, themetadata_filefile will only be scanned for the following fields:channel: The upload target channel name (seeChannel). If omitted, ‘stable’ is assumed.changelog: A description of the changes included since the last uploadInfoTheinfocommand will return metadata about the current available API. To retrieve this data, the user
can run the following command:$ click-toolbelt infoThis will show all available information about the API. Alternative, the user can retrieve only a subset of the data.Get the current API version$ click-toolbelt info versionGet the list of valid license values$ click-toolbelt info licenseGet the list of valid countries$ click-toolbelt info countryGet the list of valid channels$ click-toolbelt info channelGet the list of valid departments$ click-toolbelt info departmentData valuesDepartmentValid values can be obtained via theinfocommand (or it’s equivalent api call).Examples“Accessories”“Games”“Card Games”LicenseValid values can be obtained via theinfocommand (or it’s equivalent api call).Examples“Proprietary”“GNU GPL v3”“BSD License (Simplified)”CountryValid values can be obtained via theinfocommand (or it’s equivalent api call).Examples“AR” (Argentina)“BR” (Brazil)“GB” (United Kingdom)“US” (United States)“UY” (Uruguay)ChannelValid values can be obtained via theinfocommand (or it’s equivalent api call).Examples“stable”“proposed”“alpha”