Avia's mentioned at one point that we might have misunderstood the spec at this section, and that in fact it can be possible to pass arbitrary inputs into operations regardless of the interface definition - which would mean this notion of "configuration" might be unnecessary.
Also, note that the doc page is talking about "executors", which is confusing as that's a different concept in ARIA (see the base executor class); Supposedly up until now we've simply called these "operation plugins". On Sat, Sep 9, 2017 at 1:43 AM, Tal Liron <t...@cloudify.co> wrote: > Yes: > https://cwiki.apache.org/confluence/display/ARIATOSCA/ > Execution+Configuration > > On Fri, Sep 8, 2017 at 4:45 PM, DeWayne Filppi <dewa...@cloudify.co> > wrote: > > > I see in the examples a list of dependencies for scripts in operations, > for > > example: > > > > implementation: > > primary: scripts/configure.sh > > dependencies: > > - "ssh.user > { get_input: ssh_username }" > > - "ssh.key_filename > { get_input: private_key_path }" > > - "ssh.address > { get_attribute: [ virtual_ip, > > floating_ip_address ] }" > > > > The spec seems to indicate that the dependency list is for resources that > > need to be made available so the main script can be run. Clearly that > > isn't the case in the example. Is this '>' syntax documented anywhere? > > >
