Skip to content

Commit 67f0cb9

Browse files
author
Glenn Matthews
committed
Merge branch 'release/0.9.1'
2 parents 4d3779a + 2752596 commit 67f0cb9

File tree

57 files changed

+3594
-647
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

57 files changed

+3594
-647
lines changed

CHANGELOG.md

+23-2
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,29 @@
22
All notable changes to this project will be documented in this file.
33
This project adheres to [Semantic Versioning](http://semver.org/).
44

5-
## [0.9.0] - 2015-06-22
5+
## [Unreleased]
6+
7+
## [0.9.1] - 2015-08-13
8+
### Added
9+
- Added CONTRIBUTING.md
10+
- Added README-creating-types-providers.md and associated templates.
11+
- Added SUPPORT.md
12+
- Added Beaker test cases for cisco_command_config, file, package, and service providers.
13+
14+
### Fixed
15+
- 'puppet resource cisco_vtp' now works properly.
16+
- cisco_interface, cisco_ospf_vrf, and cisco_vlan now properly handle destroy/recreate scenarios.
17+
- Added missing methods in cisco_ospf_vrf provider.
18+
- Style cleanup of many Beaker test scripts.
19+
- Fixed title pattern error in 'puppet resource cisco_snmp_group'.
20+
- Avoid inadvertently suppressing relevant exceptions.
21+
- Added dotted-decimal munging for area in cisco_interface_ospf
22+
- Modified template placeholder names to meet lint reqs
23+
24+
## 0.9.0 - 2015-07-24
625
### Added
7-
- Initial release of cisco-ciscolib_nxos module for puppet, supporting Cisco NX-OS software release 7.0(3)I2(1) on Cisco Nexus switch platforms: N95xx, N93xx, N30xx and N31xx.
26+
- Initial release of puppetlabs-ciscopuppet module, supporting Cisco NX-OS software release 7.0(3)I2(1) on Cisco Nexus switch platforms: N95xx, N93xx, N30xx and N31xx.
827
- Please note: 0.9.0 is an EFT pre-release for a limited audience with access to NX-OS 7.0(3)I2(1). Additional code changes may occur in 0.9.x prior to the final 1.0.0 release.
928

29+
[unreleased]: https://github.com/cisco/cisco-network-puppet-module/compare/v0.9.1...develop
30+
[0.9.1]: https://github.com/cisco/cisco-network-puppet-module/compare/v0.9.0...v0.9.1

CONTRIBUTING.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# How to Contribute
2+
Cisco Network Elements support a rich set of features to make networks robust, efficient and secure. This project enables Cisco Network Elements to be managed by Puppet by defining a set of resource types and providers. This set is expected to grow with contributions from Cisco, Puppet Labs and third-party alike. Contributions to this project are welcome. To ensure code quality, contributers will be requested to follow a few guidelines.
3+
4+
## Getting Started
5+
6+
* Create a [GitHub account](https://github.com/signup/free)
7+
* Make sure you have a [cisco.com](http://cisco.com) account, if you need access to a Network Simulator to test your code.
8+
9+
## Making Changes
10+
11+
* Fork the repository
12+
* Pull a branch under the "develop" branch for your changes.
13+
* Follow all guidelines documented in [README-creating-types-providers](#README-creating-types-providers.md)
14+
* Make changes in your branch.
15+
* Testing
16+
* TBD: Add beaker test cases to validate your changes.
17+
* Run all the tests to ensure there was no collateral damage to existing code.
18+
* Check for unnecessary whitespace with `git diff --check`
19+
* Run `rubocop --lint` against all changed files. See [https://rubygems.org/gems/rubocop](https://rubygems.org/gems/rubocop)
20+
* TBD: Run [puppet-lint](https://rubygems.org/gems/puppet-lint) against changed files.
21+
* For new resources, add a 'demo' entry to examples/demo_install.rb
22+
* Ensure that your commit messages clearly describe the problem you are trying to solve and the proposed solution.
23+
24+
## Submitting Changes
25+
26+
* All contributions you submit to this project are voluntary and subject to the terms of the Apache 2.0 license.
27+
* Submit a pull request for commit approval to the "develop" branch.
28+
* A core team consisting of Cisco and Puppet Labs employees will looks at Pull Request and provide feedback.
29+
* After feedback has been given we expect responses within two weeks. After two weeks we may close the pull request if it isn't showing any activity.
30+
31+
# Additional Resources
32+
33+
* [General GitHub documentation](http://help.github.com/)
34+
* [GitHub pull request documentation](http://help.github.com/send-pull-requests/)
35+
* \#puppet-dev IRC channel on freenode.org ([Archive](https://botbot.me/freenode/puppet-dev/))
36+
* [puppet-dev mailing list](https://groups.google.com/forum/#!forum/puppet-dev)

0 commit comments

Comments
 (0)