Skip to content

Conversation

@DavidS
Copy link
Contributor

@DavidS DavidS commented May 9, 2019

There were some inaccuracies vs the actual implementation and some copy
editing to make the document flow better.

There were some inaccuracies vs the actual implementation and some copy
editing to make the document flow better.
@DavidS DavidS requested review from clairecadman and da-ar May 9, 2019 09:43
This commit makes minor grammatical edits.
### Legacy Support

Before Puppet 6.X (TBD), remote resources were only supported through the `Puppet::Util::NetworkDevice` namespace. To make a module useful on these older versions, a shim `Device` class needs to be provided to connect the dots:
Before the Resource API, remote resources were only supported through the `Puppet::Util::NetworkDevice` namespace. To connect your transport to what Puppet expects, you need to provide a shim `Device` class.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe change: "To connect your transport to what Puppet expects, you need to provide a shim Device class."

To: "To connect your transport in a way that Puppet understands, you need to provide a shim Device class."

If this is what it means? If not please clarify.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That sounds so much better.

Inheriting from `Puppet::ResourceApi::Transport::Wrapper` will ensure that the necessary `Device` methods will be implemented using your transport.
Inheriting from `Puppet::ResourceApi::Transport::Wrapper` ensures that the necessary `Device` methods are implemented using your transport. Specify the transport name in the `super` call to make the connection.
> Note that because of the way the Resource API is bundled with Puppet agent packages, agent versions 6.0 through 6.3 are incompatible with this way of executing remote content. These versions will not be supported after [PE 2019.0 in August 2019](https://puppet.com/misc/puppet-enterprise-lifecycle).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2019.0 has been out for a while? This sounds like it comes out in August 2019.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

changed to These versions will not be supported after [support for PE 2019.0 ends in August 2019](https://puppet.com/misc/puppet-enterprise-lifecycle). for clarity

@DavidS
Copy link
Contributor Author

DavidS commented May 14, 2019

@clairecadman fixed the last two issues. Please merge if you're satisfied.

@clairecadman clairecadman merged commit 3ae711f into puppetlabs:master May 14, 2019
@DavidS DavidS deleted the FM-7878-update-transports branch June 10, 2019 15:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants