-
Notifications
You must be signed in to change notification settings - Fork 581
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
Revert "(CONT-801) Deprecate uriescape.rb" #1402
base: main
Are you sure you want to change the base?
Conversation
This reverts commit 799d608. While uriescape was deprecated for Puppet 8 in puppetlabs#1307 it was already fixed earlier for Puppet 8 and ruby 3 in puppetlabs#1195 It is unclear to me why this function was deprecated. * Fixes puppetlabs#1401
CLA signed in agreement between CERN IT and Puppetlabs. |
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.
In case that we do proceed with this: you need to update the comments on line 6 & 7.
On the question if we should proceed: I'm not sure if this is a good idea, I don't know. there's a good reason it was dropped in Ruby 3: the whole idea behind the function is sketchy. I'm more a fan of explicit URL construction where you pass the parameters unescaped and then it correctly constructs the URL.
Redundant comments removed. I only use it one place to escape
when pulling metrics out of PuppetServer. Does a url from component function exist ? |
https://docs.knapsackpro.com/2020/uri-escape-is-obsolete-percent-encoding-your-query-string suggests |
Summary
This reverts commit 799d608.
While uriescape was deprecated for Puppet 8 in #1307 it was already fixed earlier for Puppet 8 and ruby 3 in #1195
It is unclear to me why this function was deprecated.
Additional Context
Add any additional context about the problem here.
Function was deprecated on Puppet 8.
Related Issues (if any)
Checklist
puppet apply
)