bolt 0.5.0 → 0.5.1

Sign up to get free protection for your applications and to get access to all the features.

Potentially problematic release.


This version of bolt might be problematic. Click here for more details.

checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: a2f060b4f462b01b52b2124b466b31afb8f5d4a5
4
- data.tar.gz: 1d3384d30e628a6ec5ccac3b8ed906119d78ae16
3
+ metadata.gz: 9e58990a30c659e55cfa6a9414baddbb4e5f7f4f
4
+ data.tar.gz: 0eb8ae695aa463156484836b7d439531eaac7a79
5
5
  SHA512:
6
- metadata.gz: 29385451ff01d103ea9f916c4e4241ce740401a45624d7644d205e5ee0064fa5f035702d13d0b542e723b2de25d6662bd69fb9182eb8300f72ccdf2427169cf3
7
- data.tar.gz: e2504ed3ab58c8dd2828b715df0ffd0bfabfcaf2e3bf2bb9679cd6e0794c03a33def73dbc439968d4cfe8c18491df438f1ffd097371d0eede7db2a16d758f44f
6
+ metadata.gz: 3b974ec47cff910a4c70681503abb723b7d9dc8f0182b6b85028bf35ae487c4bec2a6cb5015165708d74ac822f7c28e04777db2c9e74969d15e5390712aef26e
7
+ data.tar.gz: c43c7890532c703505517d150fb546899f7b4992d91846eb889bcb86ae6885dc62b0fe88d0b2d91aabc31ba82463b05a8a9eff2c10e8c071071ee8f153874c97
@@ -0,0 +1,46 @@
1
+ # Contributor Covenant Code of Conduct
2
+
3
+ ## Our Pledge
4
+
5
+ In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
+
7
+ ## Our Standards
8
+
9
+ Examples of behavior that contributes to creating a positive environment include:
10
+
11
+ * Using welcoming and inclusive language
12
+ * Being respectful of differing viewpoints and experiences
13
+ * Gracefully accepting constructive criticism
14
+ * Focusing on what is best for the community
15
+ * Showing empathy towards other community members
16
+
17
+ Examples of unacceptable behavior by participants include:
18
+
19
+ * The use of sexualized language or imagery and unwelcome sexual attention or advances
20
+ * Trolling, insulting/derogatory comments, and personal or political attacks
21
+ * Public or private harassment
22
+ * Publishing others' private information, such as a physical or electronic address, without explicit permission
23
+ * Other conduct which could reasonably be considered inappropriate in a professional setting
24
+
25
+ ## Our Responsibilities
26
+
27
+ Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
+
29
+ Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
+
31
+ ## Scope
32
+
33
+ This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
+
35
+ ## Enforcement
36
+
37
+ Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at conduct@puppet.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
+
39
+ Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
+
41
+ ## Attribution
42
+
43
+ This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
44
+
45
+ [homepage]: http://contributor-covenant.org
46
+ [version]: http://contributor-covenant.org/version/1/4/
data/CONTRIBUTING.md ADDED
@@ -0,0 +1,27 @@
1
+ # Contributing
2
+
3
+ ## Issues
4
+
5
+ Please submit new issues on the GitHub issue tracker: https://github.com/puppetlabs/bolt/issues
6
+
7
+ Internally, Puppet uses JIRA for tracking work, so nontrivial bugs or enhancement requests may migrate to JIRA tickets
8
+ in the "BOLT" project: https://tickets.puppetlabs.com/browse/BOLT/
9
+
10
+ ## Pull Requests
11
+
12
+ Pull requests are also welcome on GitHub: https://github.com/puppetlabs/bolt
13
+
14
+ As with other open-source projects managed by Puppet, Inc we require contributors to digitally sign the Contributor
15
+ License Agreement before we can accept your pull request: https://cla.puppet.com
16
+
17
+ ## Testing
18
+
19
+ Some tests require a Windows or Linux VM. Execute `vagrant up` to bring these up with the Vagrantfile included with the `bolt` gem. Any tests that require this are tagged with `:vagrant` in rspec.
20
+
21
+ To run all tests, run:
22
+
23
+ $ bundle exec rake test
24
+
25
+ To exclude tests that rely on Vagrant, run:
26
+
27
+ $ bundle exec rake unit
data/README.md CHANGED
@@ -319,27 +319,8 @@ Thank you to [Marcin Bunsch](https://github.com/marcinbunsch) for allowing Puppe
319
319
 
320
320
  ## Contributing
321
321
 
322
- Please submit new issues on the GitHub issue tracker: https://github.com/puppetlabs/bolt/issues
323
-
324
- Pull requests are also welcome on GitHub: https://github.com/puppetlabs/bolt
325
-
326
- As with other open-source projects managed by Puppet, Inc we require contributors to digitally sign the Contributor
327
- License Agreement before we can accept your pull request: https://cla.puppet.com
328
-
329
- Internally, Puppet uses JIRA for tracking work, so nontrivial bugs or enhancement requests may migrate to JIRA tickets
330
- in the "BOLT" project: https://tickets.puppetlabs.com/browse/BOLT/
331
-
332
- ## Testing
333
-
334
- Some tests require a Windows or Linux VM. Execute `vagrant up` to bring these up with the Vagrantfile included with the `bolt` gem. Any tests that require this are tagged with `:vagrant` in rspec.
335
-
336
- To run all tests, run:
337
-
338
- $ bundle exec rake test
339
-
340
- To exclude tests that rely on Vagrant, run:
341
-
342
- $ bundle exec rake unit
322
+ We welcome error reports and pull requests to Bolt. See
323
+ [CONTRIBUTING.md](./CONTRIBUTING.md) for how to help.
343
324
 
344
325
  ## FAQ
345
326
 
data/lib/bolt/version.rb CHANGED
@@ -1,3 +1,3 @@
1
1
  module Bolt
2
- VERSION = '0.5.0'.freeze
2
+ VERSION = '0.5.1'.freeze
3
3
  end
@@ -60,7 +60,7 @@ class TaskInstantiator
60
60
 
61
61
  @type_hash_t = tf.struct(
62
62
  tf.optional('description') => tf.string,
63
- tf.optional('puppet_task_version') => tf.string,
63
+ tf.optional('puppet_task_version') => tf.integer,
64
64
  tf.optional('supports_noop') => tf.boolean,
65
65
  tf.optional('input_method') => tf.enum('stdin', 'environment'),
66
66
  'parameters' => params_t,
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: bolt
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.0
4
+ version: 0.5.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Puppet
8
8
  autorequire:
9
9
  bindir: exe
10
10
  cert_chain: []
11
- date: 2017-10-10 00:00:00.000000000 Z
11
+ date: 2017-10-11 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: net-ssh
@@ -267,6 +267,8 @@ files:
267
267
  - ".rspec"
268
268
  - ".rubocop.yml"
269
269
  - ".travis.yml"
270
+ - CODE_OF_CONDUCT.md
271
+ - CONTRIBUTING.md
270
272
  - Gemfile
271
273
  - INSTALL.md
272
274
  - LICENSE