sshkit 1.11.1 → 1.11.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +9 -1
- data/README.md +3 -3
- data/lib/sshkit/host.rb +1 -1
- data/lib/sshkit/version.rb +1 -1
- metadata +3 -3
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 942b003ed89d1b23971fcc2a90f9df45ad13894f
|
4
|
+
data.tar.gz: c3b93ab5ba8c4e3768229cd6fabc0121aaaf9a5e
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 230cd5e66474858207fccfe497d9e194e0e5fb3455350eb8c189766cd5e276b16309b3193ebfd33c69951fe4ca61258cace638dc55e3aae2f5610f1a57b1d0b2
|
7
|
+
data.tar.gz: e4376a240351954bf3d26d4f9c22e435dd6079d4516fd92805d640f25ad71af1830b2a4f6ada9c2c2cb0e2c038be9e85b076442d002a8e492933a303a7e21ef3
|
data/CHANGELOG.md
CHANGED
@@ -8,6 +8,13 @@ appear at the top.
|
|
8
8
|
* Add your entries below here, remember to credit yourself however you want
|
9
9
|
to be credited!
|
10
10
|
|
11
|
+
## [1.11.2][] (2016-07-29)
|
12
|
+
|
13
|
+
### Bug fixes
|
14
|
+
|
15
|
+
* Fixed a crash occurring when `Host@keys` was set to a non-Enumerable.
|
16
|
+
@xavierholt [PR #360](https://github.com/capistrano/sshkit/pull/360)
|
17
|
+
|
11
18
|
## [1.11.1][] (2016-06-17)
|
12
19
|
|
13
20
|
### Bug fixes
|
@@ -637,6 +644,7 @@ version `0.0.5`.
|
|
637
644
|
|
638
645
|
First release.
|
639
646
|
|
640
|
-
[Unreleased]: https://github.com/capistrano/sshkit/compare/v1.11.
|
647
|
+
[Unreleased]: https://github.com/capistrano/sshkit/compare/v1.11.2...HEAD
|
648
|
+
[1.11.2]: https://github.com/capistrano/sshkit/compare/v1.11.1...v1.11.2
|
641
649
|
[1.11.1]: https://github.com/capistrano/sshkit/compare/v1.11.0...v1.11.1
|
642
650
|
[1.11.0]: https://github.com/capistrano/sshkit/compare/v1.10.0...v1.11.0
|
data/README.md
CHANGED
@@ -94,16 +94,16 @@ When used inside a block in this way, `as()` and `within()` will guard
|
|
94
94
|
the block they are given with a check.
|
95
95
|
|
96
96
|
In the case of `within()`, an error-raising check will be made that the directory
|
97
|
-
exists; for `as()` a simple call to `sudo
|
97
|
+
exists; for `as()` a simple call to `sudo -u <user> -- sh -c <command>'` wrapped in a check for
|
98
98
|
success, raising an error if unsuccessful.
|
99
99
|
|
100
100
|
The directory check is implemented like this:
|
101
101
|
|
102
102
|
if test ! -d <directory>; then echo "Directory doesn't exist" 2>&1; false; fi
|
103
103
|
|
104
|
-
And the user switching test implemented like this:
|
104
|
+
And the user switching test is implemented like this:
|
105
105
|
|
106
|
-
if ! sudo
|
106
|
+
if ! sudo -u <user> whoami > /dev/null; then echo "Can't switch user" 2>&1; false; fi
|
107
107
|
|
108
108
|
According to the defaults, any command that exits with a status other than 0
|
109
109
|
raises an error (this can be changed). The body of the message is whatever was
|
data/lib/sshkit/host.rb
CHANGED
data/lib/sshkit/version.rb
CHANGED
metadata
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
2
2
|
name: sshkit
|
3
3
|
version: !ruby/object:Gem::Version
|
4
|
-
version: 1.11.
|
4
|
+
version: 1.11.2
|
5
5
|
platform: ruby
|
6
6
|
authors:
|
7
7
|
- Lee Hambley
|
@@ -9,7 +9,7 @@ authors:
|
|
9
9
|
autorequire:
|
10
10
|
bindir: bin
|
11
11
|
cert_chain: []
|
12
|
-
date: 2016-
|
12
|
+
date: 2016-07-30 00:00:00.000000000 Z
|
13
13
|
dependencies:
|
14
14
|
- !ruby/object:Gem::Dependency
|
15
15
|
name: net-ssh
|
@@ -218,7 +218,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
218
218
|
version: '0'
|
219
219
|
requirements: []
|
220
220
|
rubyforge_project:
|
221
|
-
rubygems_version: 2.6.
|
221
|
+
rubygems_version: 2.6.6
|
222
222
|
signing_key:
|
223
223
|
specification_version: 4
|
224
224
|
summary: SSHKit makes it easy to write structured, testable SSH commands in Ruby
|