GitHub user sjcorbett opened a pull request:

    https://github.com/apache/brooklyn-server/pull/422

    SshCommandEffector + shell.env

    SshCommandEffector resolves shell.env against the target entity rather than 
always resolving it against the entity the effector is attached to. This also 
fixes the resolution of the execution directory.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/sjcorbett/brooklyn-server ssh-eff-shell-env

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/brooklyn-server/pull/422.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 #422
    
----
commit 5b9af64cb9278fd8581c88d317145b66efbc5176
Author: Sam Corbett <[email protected]>
Date:   2016-11-07T18:26:36Z

    Typos

commit 02bc3123fdf805cddcacfa5cd06a5926ebd65671
Author: Sam Corbett <[email protected]>
Date:   2016-11-07T18:28:04Z

    XmlSerialiserTest logs at debug
    
    \u001b in testIllegalXmlCharacter breaks tmux when it's printed

commit ad17113f2cd35c511154fe299050ef6409f3010d
Author: Sam Corbett <[email protected]>
Date:   2016-11-08T17:54:39Z

    Delete duplicate dependency on jackson-datatype-guava

commit 14349d1972811162b49a2db1515c7405a1bc29ac
Author: Sam Corbett <[email protected]>
Date:   2016-11-08T19:22:26Z

    Fix Debian 7 live test
    
    ami-5586a43c is not unavailable.

commit fc3394c2705ec7e945172c3170c0a37e4401c5f6
Author: Sam Corbett <[email protected]>
Date:   2016-11-09T15:26:18Z

    SshCommandEffector resolves shell.env against the target entity
    
    Rather than always resolving it against the entity the effector is
    attached to. This also fixes the resolution of the execution directory.

----


---
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.
---

Reply via email to