[Iplant-api-dev] Automatic command line generation

[Rion Dooley]

Right now the order attribute is publicly used to determine the order in which the inputs and parameters are ordered to guarantee a consistent, user-defined ordering of the respective lists contents in every response. The order attribute is also used to determine the order of operations for template variable resolution in a wrapper script at runtime. [This is a way to hack in dependency logic if you need it.] The feature you’re describing where Agave auto-generates a CLI command in leu of calling a wrapper script is not exposed publicly at the moment. It’s an alpha feature we’ve used for a while to handle some internal housekeeping and to enable interactive ssh sessions on remote systems that we use to run interactive sessions on remote systems  (think terminal API and/or remote application steering). We can talk about what makes sense to expose publicly and when, but right now we’re not planning on opening that up until, at the earliest, system groups are exposed. The likely target is when we roll out configuration support in the Tenants API, but that’s not set in stone by any means.

—
Rion 

> On Feb 24, 2015, at 9:04 PM, Matthew Vaughn <vaughn at tacc.utexas.edu> wrote:
> 
> I see reference (specifically in the inputs and parameters ‘order’ attribute) to Agave being able to automatically generate a full command line, but I don’t see from the documentation how to do this. I understand argument passing and use it to great effect, but for a use case I am exploring automatic CLI construction might come in handy.
> 
> Matt
> 
> 
> 
> _______________________________________________
> Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org
> List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev  
> One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1