-
Notifications
You must be signed in to change notification settings - Fork 17
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-7971) backwards compatibility with PE 2019.0 #82
Conversation
Codecov Report
@@ Coverage Diff @@
## master #82 +/- ##
=========================================
+ Coverage 99.15% 99.26% +0.1%
=========================================
Files 39 40 +1
Lines 948 1084 +136
=========================================
+ Hits 940 1076 +136
Misses 8 8
Continue to review full report at Codecov.
|
c80e0ee
to
60594c2
Compare
60594c2
to
bfd6e1b
Compare
|
This is blocked for timebeing on a release of 1.6.4 RSAPI to rubygems |
11408ec
to
911314b
Compare
This code is a horrible workaround for the transport work that this module was converted to support but meant that current STS puppet versions would not work. This code can be reverted in August 2019 once 2019.0 STS ends.
This is to satisfy the condition that the version of bolt on a 6.0.x PE instalation may use the 1.6.x RSAPI version.
Example of a success with 1.6.x RSAPI and bolt:
```
Started on cgnodswd2r9rm9e.delivery.puppetlabs.net...
Finished on cgnodswd2r9rm9e.delivery.puppetlabs.net:
{
"apikey": "xxx"
}
Successful on 1 node: cgnodswd2r9rm9e.delivery.puppetlabs.net
Ran on 1 node in 2.85 seconds
```
911314b
to
7d38a29
Compare
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.
Looks good to me.
This PR will add support to the module to work with RSAPI 1.6.x that Puppet 6.0.x is shipped with. This PR could be reverted once STS of PE 2019.0 is over.