Merge branch 'hotfix/1.0.1'

Author: mikewiebe

CHANGELOG.md

@@ -2,6 +2,10 @@
 All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 
+## [1.0.1] - 2015-09-18
+### Fixed
+- Fixed broken documentation links
+
 ## [1.0.0] - 2015-08-28
 ### Added
 - New facts `cisco_node_utils` and `cisco_nxapi` report the installed version of these gems.

CONTRIBUTING.md

@@ -10,7 +10,7 @@ Cisco Network Elements support a rich set of features to make networks robust, e
 
 * Fork the repository
 * Pull a branch under the "develop" branch for your changes.
-* Follow all guidelines documented in [README-creating-types-providers](README-creating-types-providers.md)
+* Follow all guidelines documented in [README-develop-types-providers](docs/README-develop-types-providers.md)
 * Make changes in your branch.
 * Testing
   * Add beaker test cases to validate your changes.

docs/README-agent-install.md

@@ -243,10 +243,10 @@ This file can be used to override the default Puppet settings. At a minimum, the
 
 See the following references for more puppet.conf settings:
 
-<https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html>
-<https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html>
-<https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html>
-<https://docs.puppetlabs.com/references/latest/configuration.html>
+* https://docs.puppetlabs.com/puppet/latest/reference/config_important_settings.html
+* https://docs.puppetlabs.com/puppet/latest/reference/config_about_settings.html
+* https://docs.puppetlabs.com/puppet/latest/reference/config_file_main.html
+* https://docs.puppetlabs.com/references/latest/configuration.html
 
 #### Run the Puppet Agent
 

docs/README-beaker-agent-install.md

@@ -7,9 +7,8 @@
 3. [Beaker Installer Configuration](#beaker-install-config)
 4. [Automated Puppet Agent Install: bash-shell](#install-bs)
 5. [Automated Puppet Agent Install: guestshell](#install-gs)
-6. [References](#references)
-7. [Limitations](#limitations)
-8. [License Information](#license-information)
+6. [Limitations](#limitations)
+7. [License Information](#license-information)
 
 ## <a name="overview">Overview</a>
 
@@ -64,8 +63,8 @@ end
 The following commands should be run on your Beaker workstation.
 
 ~~~
-$ git clone https://github.com/puppetlabs/cisco-ciscopuppet.git
-$ cd cisco-ciscopuppet/utilities/installer
+$ git clone https://github.com/cisco/cisco-network-puppet-module.git 
+$ cd cisco-network-puppet-module/utilities/installer/ 
 ~~~
 
 ### Copy and modify the SAMPLE* configuration files.

docs/README-develop-types-providers.md

@@ -22,19 +22,19 @@ This document is a guide for writing new Puppet resource types and providers for
 
 There are multiple components involved when creating new resources. This document focuses on the type and provider files:
 
-![1](docs/tp_files.png)
+![1](tp_files.png)
 
 * Every resource is associated with a [resource type](https://docs.puppetlabs.com/puppet/latest/reference/lang_resources.html), which determines the kind of configuration it manages.
 
 * [Resource providers](https://docs.puppetlabs.com/guides/provider_development.html) are essentially backends that implement support for a specific implementation of a given resource type.
 
-* The types and providers work in conjunction with a node\_utils API, which is the interface between Puppet agent and the NX-OS CLI. Please see the [README-develop-node-utils-APIs.md] (https://github.com/cisco/cisco-network-node-utils/blob/master/README-develop-node-utils-APIs.md) guide for more information on writing node_utils APIs.
+* The types and providers work in conjunction with a node\_utils API, which is the interface between Puppet agent and the NX-OS CLI. Please see the [README-develop-node-utils-APIs.md] (https://github.com/cisco/cisco-network-node-utils/blob/master/docs/README-develop-node-utils-APIs.md) guide for more information on writing node_utils APIs.
 
-This document relies heavily on example code. The examples in this document can be written independently, but they are intended to work in conjuction with the example node_utils APIs created in the [README-develop-node_utils-APIs.md](https://github.com/cisco/cisco-network-node-utils/blob/master/README-develop-node-utils-APIs.md) guide. The examples in that guide are based on code templates for the `feature bash-shell` CLI and the `router eigrp` CLI. Note that some people prefer to write the node_utils API before the resource types and providers, while others might prefer the opposite workflow.
+This document relies heavily on example code. The examples in this document can be written independently, but they are intended to work in conjuction with the example node_utils APIs created in the [README-develop-node_utils-APIs.md](https://github.com/cisco/cisco-network-node-utils/blob/master/docs/README-develop-node-utils-APIs.md) guide. The examples in that guide are based on code templates for the `feature bash-shell` CLI and the `router eigrp` CLI. Note that some people prefer to write the node_utils API before the resource types and providers, while others might prefer the opposite workflow.
 
 ## <a name="clone">Start here: Clone the Repo</a>
 
-Please see the [CONTRIBUTING](#CONTRIBUTING) document for workflow instructions. In general, fork the ciscopuppet repository for your changes and submit a pull request when it is ready for commit.
+Please see the [CONTRIBUTING](../CONTRIBUTING.md) document for workflow instructions. In general, fork the ciscopuppet repository for your changes and submit a pull request when it is ready for commit.
 
 First install the code base. Clone the ciscopuppet repo into a workspace:
 
@@ -296,7 +296,7 @@ Inspecting 2 files
 
 ## <a name="comp_example">Complex Example: router eigrp</a>
 
-This resource type and provider exercise will build on the router_eigrp API example shown in the cisco node_utils [README-develop-node-utils-APIs](https://github.com/cisco/cisco-network-node-utils/blob/master/README-develop-node-utils-APIs.md) document.
+This resource type and provider exercise will build on the router_eigrp API example shown in the cisco node_utils [README-develop-node-utils-APIs](https://github.com/cisco/cisco-network-node-utils/blob/master/docs/README-develop-node-utils-APIs.md) document.
 The router_eigrp node_utils example created a new API for the cli below:
 
 ~~~
@@ -699,4 +699,4 @@ Inspecting 2 files
 
 ## <a name="next">Next Steps</a>
 
-Please see the [CONTRIBUTING](#CONTRIBUTING) document for workflow instructions.
+Please see the [CONTRIBUTING](../CONTRIBUTING.md) document for workflow instructions.

docs/README-maintainers.md

@@ -1,6 +1,6 @@
 # Maintainers Guide
 
-Guidelines for the core maintainers of the ciscopuppet project - above and beyond the [general developer guidelines](https://github.com/cisco/cisco-network-puppet-module/blob/develop/CONTRIBUTING.md).
+Guidelines for the core maintainers of the ciscopuppet project - above and beyond the [general developer guidelines](../CONTRIBUTING.md).
 
 ## Accepting Pull Requests
 
@@ -77,4 +77,4 @@ When we agree as a team that a new release should be published, the process is a
     git push --tags
     ```
 
-6. Add release notes on GitHub, for example `https://github.com/cisco/cisco-network-puppet-module/releases/new?tag=v1.0.1`. Usually this will just be a copy-and-paste of the relevant section of the `CHANGELOG.md`.
+6. Add release notes on GitHub, for example `https://github.com/cisco/cisco-network-puppet-module/releases/new?tag=v1.0.1`. Usually this will just be a copy-and-paste of the relevant section of the `CHANGELOG.md`.

docs/README-package-provider.md

@@ -4,10 +4,8 @@
 
 1. [Overview](#overview)
 2. [Syntax](#syntax)
-3. [Examples](examples)
-9. [References](#references)
-10. [Limitations](#limitations)
-11. [Known Issues](#issues)
+3. [Examples](#examples)
+4. [References](#references)
 
 ## <a name="overview">Overview</a>
 
@@ -51,7 +49,7 @@ where:
 * `provider`: Optional. Set to 'nxapi' if installling a Cisco package.
 
 
-## <a name="Examples">Examples</a>
+## <a name="examples">Examples</a>
 
 * **Cisco RPMs**
 

examples/README.md

@@ -20,7 +20,7 @@ This document describes how to use the example demo manifest files contained wit
 * `demo_bgp_[ipv4|ipv6]_site.pp`
   * Provides sample manifests to configure bgp using the `cisco_command_config` provider.
 
-**Note:** Before following the steps in this guide make sure the puppet agent is [installed and configured.](https://github.com/puppetlabs/cisco-ciscopuppet/blob/master/README-AGENT-INSTALL.md)
+**Note:** Before following the steps in this guide make sure the puppet agent is [installed and configured.](../docs/README-AGENT-INSTALL.md)
 
 ## <a name="setup">Initial Setup</a>
 

metadata.json

@@ -1,6 +1,6 @@
 {
   "name": "puppetlabs-ciscopuppet",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "author": "cisco",
   "summary": "Cisco Puppet providers and types for NX-OS devices",
   "license": "Apache-2.0",