-
Notifications
You must be signed in to change notification settings - Fork 65
(FM-7878) Update transport docs #139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(FM-7878) Update transport docs #139
Conversation
There were some inaccuracies vs the actual implementation and some copy editing to make the document flow better.
This commit makes minor grammatical edits.
language/resource-api/README.md
Outdated
| ### 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
language/resource-api/README.md
Outdated
| 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). |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
|
@clairecadman fixed the last two issues. Please merge if you're satisfied. |
There were some inaccuracies vs the actual implementation and some copy
editing to make the document flow better.