vcloud-core 0.0.11 → 0.0.12

Sign up to get free protection for your applications and to get access to all the features.
@@ -1,3 +1,9 @@
1
+ ## 0.0.12 (2014-04-22)
2
+
3
+ Bugfix:
4
+
5
+ - move to require fog v1.22 to allow for issue with progress task bar exposed with upgrade to vCloud Director 5.5
6
+
1
7
  ## 0.0.11 (2014-04-01)
2
8
 
3
9
  Features:
data/README.md CHANGED
@@ -18,18 +18,6 @@ Or install it yourself as:
18
18
 
19
19
  $ gem install vcloud-core
20
20
 
21
- ## Usage
22
-
23
- TODO
24
-
25
- ## Contributing
26
-
27
- 1. Fork it
28
- 2. Create your feature branch (`git checkout -b my-new-feature`)
29
- 3. Commit your changes (`git commit -am 'Add some feature'`)
30
- 4. Push to the branch (`git push origin my-new-feature`)
31
- 5. Create new Pull Request
32
-
33
21
  ## VCloud Query
34
22
 
35
23
  ### Get results from the vCloud Query API
@@ -101,3 +89,32 @@ Entity metadata queries have their own subsyntax incorporating the value types:
101
89
 
102
90
  See http://pubs.vmware.com/vcd-51/topic/com.vmware.vcloud.api.doc_51/GUID-4FD71B6D-6797-4B8E-B9F0-618F4ACBEFAC.html for details.
103
91
 
92
+ ## Testing
93
+
94
+ Default target: `bundle exec rake`
95
+ Runs the unit tests and feature tests.
96
+
97
+ * Unit tests only: `bundle exec rake spec`
98
+ * Feature tests only: `bundle exec rake feature`
99
+ * Integration tests: `bundle exec rake integration`
100
+
101
+ ### setting up and describing your environment for test runs
102
+
103
+ You need access to a suitable vCloud Director organization to run the integration tests - it also needs some basic
104
+ configuration: an Edge Gateway, and a routed network.
105
+ It is not necessarily safe to run them against an existing environment, unless care is taken with the entities being
106
+ tested.
107
+
108
+ A number of ENV vars specifying items under test in the environment need to be set for the tests to run successfully.
109
+
110
+ - `VCLOUD_EDGE_GATEWAY`: _name of edge gateway under test_
111
+ - `VCLOUD_NETWORK1_ID`: _Id of network under test_
112
+ - `VCLOUD_PROVIDER_NETWORK_ID`: _Id of the uplink network (or external network) of the VCLOUD_EDGE_GATEWAY under test_
113
+
114
+ ## Contributing
115
+
116
+ 1. Fork it
117
+ 2. Create your feature branch (`git checkout -b my-new-feature`)
118
+ 3. Commit your changes (`git commit -am 'Add some feature'`)
119
+ 4. Push to the branch (`git push origin my-new-feature`)
120
+ 5. Create new Pull Request
data/Rakefile CHANGED
@@ -1,5 +1,7 @@
1
- require 'bundler/gem_tasks'
2
1
  require 'rspec/core/rake_task'
2
+ require 'cucumber/rake/task'
3
+
4
+ task :default => [:spec, :feature]
3
5
 
4
6
  RSpec::Core::RakeTask.new(:spec) do |task|
5
7
  # Set a bogus Fog credential, otherwise it's possible for the unit
@@ -10,7 +12,10 @@ RSpec::Core::RakeTask.new(:spec) do |task|
10
12
  task.pattern = FileList['spec/vcloud/**/*_spec.rb']
11
13
  end
12
14
 
13
- task :default => [:spec]
15
+ Cucumber::Rake::Task.new(:feature) do |t|
16
+ t.cucumber_opts = "--format pretty --no-source"
17
+ t.fork = false
18
+ end
14
19
 
15
20
  RSpec::Core::RakeTask.new('integration') do |t|
16
21
  t.pattern = FileList['spec/integration/**/*_spec.rb']
@@ -0,0 +1,16 @@
1
+ require 'aruba/cucumber'
2
+ require 'methadone/cucumber'
3
+
4
+ ENV['PATH'] = "#{File.expand_path(File.dirname(__FILE__) + '/../../bin')}#{File::PATH_SEPARATOR}#{ENV['PATH']}"
5
+ LIB_DIR = File.join(File.expand_path(File.dirname(__FILE__)),'..','..','lib')
6
+
7
+ Before do
8
+ # Using "announce" causes massive warnings on 1.9.2
9
+ @puts = true
10
+ @original_rubylib = ENV['RUBYLIB']
11
+ ENV['RUBYLIB'] = LIB_DIR + File::PATH_SEPARATOR + ENV['RUBYLIB'].to_s
12
+ end
13
+
14
+ After do
15
+ ENV['RUBYLIB'] = @original_rubylib
16
+ end
@@ -0,0 +1,14 @@
1
+ Feature: "vcloud-query" works as a useful command-line tool
2
+ In order to use "vcloud-query" from the CLI
3
+ I want to have it behave like a typical Unix tool
4
+ So I don't get surpised
5
+
6
+ Scenario: Common arguments work
7
+ When I get help for "vcloud-query"
8
+ Then the exit status should be 0
9
+ And the banner should be present
10
+ And the banner should document that this app takes options
11
+ And the following options should be documented:
12
+ |--version|
13
+ And the banner should document that this app's arguments are:
14
+ |type|
@@ -1,5 +1,5 @@
1
1
  module Vcloud
2
2
  module Core
3
- VERSION = '0.0.11'
3
+ VERSION = '0.0.12'
4
4
  end
5
5
  end
@@ -22,10 +22,12 @@ Gem::Specification.new do |s|
22
22
 
23
23
  s.required_ruby_version = '>= 1.9.2'
24
24
 
25
- s.add_runtime_dependency 'fog', '>= 1.21.0'
25
+ s.add_runtime_dependency 'fog', '>= 1.22.0'
26
26
  s.add_runtime_dependency 'methadone'
27
+ s.add_development_dependency 'aruba', '~> 0.5.3'
28
+ s.add_development_dependency 'cucumber', '~> 1.3.10'
27
29
  s.add_development_dependency 'rake'
28
30
  s.add_development_dependency 'rspec', '~> 2.14.1'
29
31
  s.add_development_dependency 'simplecov', '~> 0.8.2'
30
- s.add_development_dependency "gem_publisher", "1.2.0"
32
+ s.add_development_dependency 'gem_publisher', '1.2.0'
31
33
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: vcloud-core
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.11
4
+ version: 0.0.12
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,7 +9,7 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2014-04-02 00:00:00.000000000 Z
12
+ date: 2014-04-22 00:00:00.000000000 Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: fog
@@ -18,7 +18,7 @@ dependencies:
18
18
  requirements:
19
19
  - - ! '>='
20
20
  - !ruby/object:Gem::Version
21
- version: 1.21.0
21
+ version: 1.22.0
22
22
  type: :runtime
23
23
  prerelease: false
24
24
  version_requirements: !ruby/object:Gem::Requirement
@@ -26,7 +26,7 @@ dependencies:
26
26
  requirements:
27
27
  - - ! '>='
28
28
  - !ruby/object:Gem::Version
29
- version: 1.21.0
29
+ version: 1.22.0
30
30
  - !ruby/object:Gem::Dependency
31
31
  name: methadone
32
32
  requirement: !ruby/object:Gem::Requirement
@@ -43,6 +43,38 @@ dependencies:
43
43
  - - ! '>='
44
44
  - !ruby/object:Gem::Version
45
45
  version: '0'
46
+ - !ruby/object:Gem::Dependency
47
+ name: aruba
48
+ requirement: !ruby/object:Gem::Requirement
49
+ none: false
50
+ requirements:
51
+ - - ~>
52
+ - !ruby/object:Gem::Version
53
+ version: 0.5.3
54
+ type: :development
55
+ prerelease: false
56
+ version_requirements: !ruby/object:Gem::Requirement
57
+ none: false
58
+ requirements:
59
+ - - ~>
60
+ - !ruby/object:Gem::Version
61
+ version: 0.5.3
62
+ - !ruby/object:Gem::Dependency
63
+ name: cucumber
64
+ requirement: !ruby/object:Gem::Requirement
65
+ none: false
66
+ requirements:
67
+ - - ~>
68
+ - !ruby/object:Gem::Version
69
+ version: 1.3.10
70
+ type: :development
71
+ prerelease: false
72
+ version_requirements: !ruby/object:Gem::Requirement
73
+ none: false
74
+ requirements:
75
+ - - ~>
76
+ - !ruby/object:Gem::Version
77
+ version: 1.3.10
46
78
  - !ruby/object:Gem::Dependency
47
79
  name: rake
48
80
  requirement: !ruby/object:Gem::Requirement
@@ -123,6 +155,8 @@ files:
123
155
  - README.md
124
156
  - Rakefile
125
157
  - bin/vcloud-query
158
+ - features/support/env.rb
159
+ - features/vcloud-query.feature
126
160
  - jenkins.sh
127
161
  - lib/vcloud/core.rb
128
162
  - lib/vcloud/core/compute_metadata.rb
@@ -190,7 +224,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
190
224
  version: '0'
191
225
  segments:
192
226
  - 0
193
- hash: 888390188831328140
227
+ hash: 3087589811732903826
194
228
  requirements: []
195
229
  rubyforge_project:
196
230
  rubygems_version: 1.8.23
@@ -198,6 +232,8 @@ signing_key:
198
232
  specification_version: 3
199
233
  summary: Core tools for interacting with VMware vCloud Director
200
234
  test_files:
235
+ - features/support/env.rb
236
+ - features/vcloud-query.feature
201
237
  - spec/integration/edge_gateway/configure_edge_gateway_services_spec.rb
202
238
  - spec/integration/edge_gateway/edge_gateway_spec.rb
203
239
  - spec/spec_helper.rb