vagrant-vmck 0.3.2 → 0.4.1

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 CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 946e9083729b16d5cced66a3245f91792b4c3df9c65aefd54d56d66afa770744
4
- data.tar.gz: a5b096ae4a356ba21aad5d3e4c42f3e97e01aa437408c8f09bab4c1c820ebf30
3
+ metadata.gz: ecdb3027a337a29f3c9d4644ca274acb66139ac7c74c3256ff4cba5bed846bd5
4
+ data.tar.gz: 931e3c8ba91c1d93eb80a3ee2629ff1cb3e473938536d363010dce12749bd306
5
5
  SHA512:
6
- metadata.gz: '0009bbd31115a4f64d7f9c3057211c971457b86dff5d3d8f641ad1049552ccff6beb801bfed993800660cd7170823c3b729250fe1d59cf43a6f3a8cfddd7e244'
7
- data.tar.gz: aac475c79a795ca4ee5bda6a4c6208f401aa42e83aca7c0c0fcbdb2bcac19e45ee85b5d0dedc88e3c65bf4962130d9368cd70dc34d07c83cfe4081e422f94ad2
6
+ metadata.gz: de86055dd4f8b3635eece5aee100c9a5316c671aa1d515ac119c25728d0e6232028ab846088ad064ab01cd24c6f5c8549db6eb578a72ebd92f9bdb6eb09ed63a
7
+ data.tar.gz: df624f1b8763657ce3295d414a1478a639cb259b35e90581121bba7db89f14498200eb1ffed77c93c98e31bdc8732241a6e2008efa99eeac82337a29208efad1
data/.drone.yml CHANGED
@@ -71,6 +71,9 @@ steps:
71
71
  when:
72
72
  event:
73
73
  - push
74
+ branch:
75
+ exclude:
76
+ - dependabot/*
74
77
 
75
78
  - name: docker push autotag + latest
76
79
  image: plugins/docker
data/Dockerfile CHANGED
@@ -7,7 +7,9 @@ ADD . .
7
7
 
8
8
  RUN set -e \
9
9
  && apt-get update -q \
10
- && apt-get install -yq wget git procps kmod rsync ruby-dev curl jq\
10
+ && apt-get install -yq wget git procps kmod rsync ruby-dev curl \
11
+ && wget https://github.com/stedolan/jq/releases/download/jq-1.6/jq-linux32 -O /usr/bin/jq \
12
+ && chmod +x /usr/bin/jq \
11
13
  && wget https://releases.hashicorp.com/vagrant/2.2.4/vagrant_2.2.4_x86_64.deb \
12
14
  && dpkg -i vagrant_2.2.4_x86_64.deb \
13
15
  && rm vagrant_2.2.4_x86_64.deb \
data/Readme.md CHANGED
@@ -28,13 +28,30 @@ The vmck provider is also packaged as a docker image:
28
28
  ./examples/docker.sh --dev --env VMCK_URL=http://10.66.60.1:9995
29
29
  ```
30
30
 
31
+
32
+ ## Development
33
+
34
+ You can test the code using `bundle exec`:
35
+
36
+ ```shell
37
+ export VMCK_URL=http://localhost:10000
38
+ export VMCK_NAME="example"
39
+ export VAGRANT_CWD=examples/box
40
+
41
+ bundle install
42
+ bundle exec vagrant up
43
+ ```
44
+
45
+
31
46
  ## Release
47
+
32
48
  1. Update `lib/vagrant-vmck/version.rb` and commit
33
49
  2. `git tag v1.2.3; git push --tags`
34
- 3. `gem install gem-release; gem release`
35
- 4. `docker build . --tag vmck/vagrant-vmck:1.2.3 --no-cache`
36
- 5. `docker build . --tag vmck/vagrant-vmck` (should reuse the previous build)
37
- 6. `docker push vmck/vagrant-vmck`
50
+
51
+ The [gempush workflow](.github/workflows/gempush.yml) takes care of the rest,
52
+ see it work away in the [actions
53
+ tab](https://github.com/vmck/vagrant-vmck/actions).
54
+
38
55
 
39
56
  ## License
40
57
 
@@ -1,5 +1,5 @@
1
1
  module VagrantPlugins
2
2
  module Vmck
3
- VERSION = "0.3.2"
3
+ VERSION = "0.4.1"
4
4
  end
5
5
  end
data/submission/launch.sh CHANGED
@@ -13,18 +13,19 @@ chmod +x script.sh
13
13
  vagrant up
14
14
  (
15
15
  set +e
16
- vagrant ssh -- 'cd /vagrant; ./script.sh' 1> result.out 2> result.err
16
+ vagrant ssh -- 'cd /vagrant; ./script.sh' &> result.out
17
17
  echo $? > result.exit_code
18
18
  )
19
19
 
20
20
  exit_code=$(cat result.exit_code)
21
- stdout="$(base64 result.out)"
22
- stderr="$(base64 result.err)"
23
-
24
- RESULT_JSON=$(jq -n \
25
- --arg out "$stdout" \
26
- --arg err "$stderr" \
27
- --arg code $exit_code \
28
- '{stdout: $out, stderr: $err, exit_code: $code,}')
29
- curl -X POST "${VMCK_CALLBACK_URL}" -d "$RESULT_JSON" \
30
- --header "Content-Type: application/json"
21
+ base64 result.out > stdout.tmp
22
+ cat stdout.tmp | tr -d '\n' > stdout
23
+
24
+ jq -n \
25
+ --rawfile out stdout \
26
+ --arg code $exit_code \
27
+ '{stdout: $out, exit_code: $code,}' > out.json
28
+
29
+ curl -X POST "${VMCK_CALLBACK_URL}" -d @out.json \
30
+ --header "Content-Type: application/json" \
31
+ --retry 20 --retry-connrefused
data/vagrant-vmck.gemspec CHANGED
@@ -21,5 +21,5 @@ Gem::Specification.new do |spec|
21
21
  spec.add_dependency "log4r"
22
22
 
23
23
  spec.add_development_dependency "bundler", "~> 2.0"
24
- spec.add_development_dependency "rake", "~> 12.3"
24
+ spec.add_development_dependency "rake", "~> 13.0"
25
25
  end
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-vmck
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.3.2
4
+ version: 0.4.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Alex Morega
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2019-10-16 00:00:00.000000000 Z
11
+ date: 2020-01-08 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: faraday
@@ -72,14 +72,14 @@ dependencies:
72
72
  requirements:
73
73
  - - "~>"
74
74
  - !ruby/object:Gem::Version
75
- version: '12.3'
75
+ version: '13.0'
76
76
  type: :development
77
77
  prerelease: false
78
78
  version_requirements: !ruby/object:Gem::Requirement
79
79
  requirements:
80
80
  - - "~>"
81
81
  - !ruby/object:Gem::Version
82
- version: '12.3'
82
+ version: '13.0'
83
83
  description: Enables Vagrant to use Vmck jobs.
84
84
  email:
85
85
  - alex@grep.ro