I actually think it still might be related to the issue I mentioned above :) if the operation input isn't set with actual values, the node property should take hold - but because of the bug I mentioned the operation input receives empty yet still set values and therefore possibly overrides the node properties.
On Thu, Aug 24, 2017 at 3:34 AM, DeWayne Filppi <dewa...@cloudify.co> wrote: > Found it. Turns out "openstack_config" in node properties is deprecated > with extreme prejudice (IOW it doesn't work). Putting it in the operation > inputs makes it work. > > On Wed, Aug 23, 2017 at 11:02 AM, Tal Liron <t...@cloudify.co> wrote: > > > Input files indeed look like that (as long as they have a .yaml suffix). > > > > If you do "aria services show -f" you can get a complete dump of the > entire > > model. Can you check that everything is correct there before we move on > to > > debugging the execution? > > > > On Wed, Aug 23, 2017 at 12:54 PM, DeWayne Filppi <dewa...@cloudify.co> > > wrote: > > > > > Having trouble with inputs when trying to run the openstack helloworld. > > I > > > provide inputs that look like this: > > > > > > ssh_username: ubuntu > > > external_network_name: public_net > > > webserver_port: 8080 > > > private_key_path: ~/dfilppi-rs.pen > > > image: some image id > > > flavor: "2" > > > openstack_config: > > > username: dewayne > > > password: xxxxxxx > > > tenant_name: dewayne-tenant > > > auth_url: https://rackspace-api.gigaspaces.com:5000/v3 > > > > > > Openstack config map entry values all become empty strings in the > > > execution. Am I specifying it wrong? There is no example inputs file > to > > > compare with, alas. > > > > > >
