vagrant-proxyconf 2.0.2 → 2.0.3

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
- SHA256:
3
- metadata.gz: 0f389b148d8815b5a0f81a851900dbea47114c3f6b60597107d7815eb6ab0fa9
4
- data.tar.gz: b3f551cedfd75ebb27d06d495b4bffee2e5832a1b45dec1065933b999939ef13
2
+ SHA1:
3
+ metadata.gz: e3b17734205419226e064520e1dabdcd04e368fb
4
+ data.tar.gz: c479e89afc35d15965a2de05855b8c2521e9dcb9
5
5
  SHA512:
6
- metadata.gz: d8a521ab63ab244683f2027ae6dc5902f9f8ff9b08514f3099ff0fcfd9e3f1105a1518fdd924f2fcb57ca53a131a5510cb877eeaefd28b3bef47eab00fe265e6
7
- data.tar.gz: 4cd46b6a73344a8d1ee2fe045d2c398c172298d6fa0c2fbda69785e76999d1748072bbf3cc832433494921b9d27dc19644125414198746cf0e236713f3ac06af
6
+ metadata.gz: 4c56154d1e9a74dc94374f8818564e350f1ea18ed576a3865c80632f1e416040b912340f3f811ad717aa53dacfc9e5a58e881e192f931c5a2eebbb7b453a8ffb
7
+ data.tar.gz: 3492607c652bc801396ee47c36550de224487a65f5db6b419c6dce3eabe04381a287f51057080c80c5844ec828589717dcde7a36a0f4a3fc499ac29ec61f2ab7
data/CHANGELOG.md CHANGED
@@ -1,4 +1,20 @@
1
- # 2.0.2 / _Not released yet_
1
+ # 2.0.4 / NOT_YET_RELEASED
2
+
3
+ # 2.0.3 / 2019-07-23
4
+
5
+ This is a bug fix release to address systemd and docker issues.
6
+
7
+ Bug Fixes:
8
+ - https://github.com/tmatilai/vagrant-proxyconf/issues/172
9
+
10
+ # 2.0.2 / 2019-07-19
11
+
12
+ This is a bug fix release, please see the issues below for furthe
13
+ details. This fix should address some Docker proxy problems when using
14
+ systemd.
15
+
16
+ Bug Fixes:
17
+ - https://github.com/tmatilai/vagrant-proxyconf/issues/172
2
18
 
3
19
  # 2.0.1 / 2019-03-31
4
20
 
@@ -33,14 +33,11 @@ module VagrantPlugins
33
33
  b.use Builtin::Call, IsEnabled do |env, b2|
34
34
  # next if !env[:result]
35
35
 
36
- # TODO: Do we really need to configure only specific proxies after the provisioner runs?
37
- # Shouldn't they already be configured by this point?
38
- # Cody Lane - Dec 2018
39
- # b2.use ConfigureDockerProxy
40
- # b2.use ConfigureGitProxy
41
- # b2.use ConfigureNpmProxy
42
- # b2.use ConfigurePearProxy
43
- # b2.use ConfigureSvnProxy
36
+ b2.use ConfigureDockerProxy
37
+ b2.use ConfigureGitProxy
38
+ b2.use ConfigureNpmProxy
39
+ b2.use ConfigurePearProxy
40
+ b2.use ConfigureSvnProxy
44
41
  end
45
42
  end
46
43
  end
@@ -1,5 +1,5 @@
1
1
  module VagrantPlugins
2
2
  module ProxyConf
3
- VERSION = '2.0.2'
3
+ VERSION = '2.0.3'
4
4
  end
5
5
  end
@@ -27,9 +27,10 @@ Vagrant.configure("2") do |config|
27
27
 
28
28
  c.vm.provider "docker" do |d|
29
29
  d.build_dir = "."
30
- d.expose = ["#{$PROXY_PORT}"]
31
30
  d.has_ssh = true
32
- d.ports = ["#{$PROXY_PORT}", "#{$PROXY_PORT}"].join(':')
31
+ d.ports = [
32
+ "#{$PROXY_PORT}:#{$PROXY_PORT}",
33
+ ]
33
34
  end
34
35
  end
35
36
 
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vagrant-proxyconf
3
3
  version: !ruby/object:Gem::Version
4
- version: 2.0.2
4
+ version: 2.0.3
5
5
  platform: ruby
6
6
  authors:
7
7
  - Teemu Matilainen
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2019-07-19 00:00:00.000000000 Z
11
+ date: 2019-07-23 00:00:00.000000000 Z
12
12
  dependencies: []
13
13
  description: A Vagrant plugin that configures the virtual machine to use proxy servers
14
14
  email:
@@ -180,7 +180,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
180
180
  version: '0'
181
181
  requirements: []
182
182
  rubyforge_project:
183
- rubygems_version: 2.7.6
183
+ rubygems_version: 2.6.14.1
184
184
  signing_key:
185
185
  specification_version: 4
186
186
  summary: A Vagrant plugin that configures the virtual machine to use proxy servers