and autocomplete the name. This format will reference the use case vars file, but bypasses this file.
Eg:
UserPost.sh
When entering input, the parameter names should match up to the help menu's provided options (cli) or the Sailthru Docs page
for that call.
http://getstarted.sailthru.com/new-for-developers-overview
*/
////Defaults or One Time Vars - In a conflict this over writes the use case file, but loses to cli input
// $api_object->setVar("id","*****@*****.**");
//Add new parameters to print out in the help screen that are exclusive to this custom Script. Can use the simpler format here or the format api classes use.
$cli_params = ["example" => "What example should be used to do"];
$api_object->createCliParameters($cli_params);
////Read in CLI Vars - In conflict takes highest priority over other inputs
$input_vars = $script->readCliArguments($argv, $api_object);
$api_object->ingestInput($input_vars["config_vars"] + $input_vars["wildcard_vars"], CliScriptAbstract::$flags["isOverride"]);
//Validates and Assigns Vars
////////// END VARS
//////////////////// START MAIN PROGRAM
////Create Client
if (CliScriptAbstract::$flags["isDefaults"]) {
$account_credentials->setAccount("defaults");
}
$client = new Sailthru_Implementation_Client($account_credentials->getKey(), $account_credentials->getSecret(), $account_credentials->getEnvironment);
////Designate Call Parameters
$call_data = $api_object->getCallData();
$endpoint = $api_object->getEndpoint();
$method = $api_object->getMethod();
////Status Output
CliScriptAbstract::$flags["isSilent"] ?: (print "Starting\n");
$template_get->setAccount($account_credentials);
require_once dirname(dirname(__DIR__)) . "/Classes/Api/Include/IncludeGet.php";
$include_get = new IncludeGet();
$include_get->setAccount($account_credentials);
// End Create API Objects
require_once dirname(dirname(__DIR__)) . "/Classes/CliScriptAbstract.php";
$script = new CliScriptAbstract();
require_once dirname(dirname(__DIR__)) . "/Classes/Client_Library/Sailthru_Implementation_Client.php";
include_once dirname(dirname(__DIR__)) . "/Setup_Files/ScriptSettings.php";
new ScriptSettings();
//Read in CLI Vars
//Add new parameters to print out in the help screen that are exclusive to this custom Script. Can use the simpler format here or the format api classes use.
// $cli_params = ["example" => "What example should be used to do"];
// $api_object->createCliParameters($cli_params);
$template_get->setDescription("Return a how compatible a given template is, or an Account's templates are, with regards to Pinning.");
$input_vars = $script->readCliArguments($argv, $template_get);
$template_get->ingestInput($input_vars["config_vars"] + $input_vars["wildcard_vars"], CliScriptAbstract::$flags["isOverride"]);
//Validates and Assigns Vars
//////////////////// START MAIN PROGRAM
////Create Client
if (CliScriptAbstract::$flags["isDefaults"]) {
$account_credentials->setAccount("defaults");
}
$client = new Sailthru_Implementation_Client($account_credentials->getKey(), $account_credentials->getSecret(), $account_credentials->getEnvironment);
////Designate Call Parameters
$call_data = $template_get->getCallData();
$bad_includes = [];
$horizon_includes = [];
////Status Output
CliScriptAbstract::$flags["isSilent"] ?: (print "Starting\n");
if ((CliScriptAbstract::$flags["isVerbose"] || CliScriptAbstract::$flags["isInteractive"]) && (!CliScriptAbstract::$flags["isQuiet"] && !CliScriptAbstract::$flags["isSilent"])) {
