GitHub user rdowner opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/476
Support scriptDir location config
This modifies `SshMachineLocation` to propagate certain config keys to
flags on `SshTool.execCommand()` and `.execScript()` invocations; the first use
of this is to propagate the `scriptDir` config. `JcloudsLocation` is also
modified to propagate this configuration. The result is that `scriptDir` can be
specified in the configuration for a jclouds-based location, and the value of
this property will be passed to every invocation of `SshTool.execScript()`.
The use case for this is to allow Brooklyn to be usable on locations where
the VM image mounts `/tmp` with `noexec`.
Also adds some integration tests to verify the correct operation of the
`scriptDir` flag.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rdowner/incubator-brooklyn ssh-script-dir
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/476.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #476
----
commit 549a3a5dcef60f96cdcded32e02537bc6d01f48f
Author: Richard Downer <[email protected]>
Date: 2015-01-27T16:06:07Z
Support scriptDir location config
This modifies SshMachineLocation to propagate certain config keys to
flags on SshTool execCommand and execScript invocations; the first use
of this is to propagate the "scriptDir" config. JcloudsLocation is also
modified to propagate this configuration. The result is that "scriptDir"
can be specified in the configuration for a jclouds-based location, and
the value of this property will be passed to every invocation of
SshTool.execScript().
The use case for this is to allow Brooklyn to be usable on locations
where the VM image mounts "/tmp" with "noexec".
Also adds some integration tests to verify the correct operation of the
scriptDir flag.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
