Skip to content

Remove dig and dig44 functions #1316

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

Merged
merged 3 commits into from
Apr 25, 2023
Merged

Conversation

MartyEwings
Copy link
Contributor

@MartyEwings MartyEwings commented Apr 25, 2023

dig became part of puppet core in Puppet 4, and even the compatibility function dig44 does not work in puppet 6 or later

this should be removed.

As part of this PR try_get_value was also removed as it was deprecated in favour of dig 6 years ago

@puppet-community-rangefinder
Copy link

dig is a function

Breaking changes to this file MAY impact these 74 modules (near match):

dig44 is a function

Breaking changes to this file MAY impact these 3 modules (near match):

This module is declared in 318 of 580 indexed public Puppetfiles.


These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

@MartyEwings
Copy link
Contributor Author

MartyEwings commented Apr 25, 2023

Looks like some of the unit tests for Other functions used Dig? ill have to figure out how to unhook all of that

*** fixed*** 2 layers of functional deprecation in this one...

Copy link
Collaborator

@bastelfreak bastelfreak left a comment

Choose a reason for hiding this comment

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

I'm surprised that the REFERENCE.md wasn't updated. The CI probably doesn't check for it (we recently implemented. I don't think you need to regenerate it for each PR, but during the release PR we need to ensure it's up2date (puppetlabs_spec_helper has a rake task for that I think). CC: @chelnak

I think vox pupuli calls this: release_checks -> validate -> https://github.com/puppetlabs/puppetlabs_spec_helper/blob/main/lib/puppetlabs_spec_helper/rake_tasks.rb#L213

@MartyEwings
Copy link
Contributor Author

I'm surprised that the REFERENCE.md wasn't updated. The CI probably doesn't check for it (we recently implemented. I don't think you need to regenerate it for each PR, but during the release PR we need to ensure it's up2date (puppetlabs_spec_helper has a rake task for that I think). CC: @chelnak

I think vox pupuli calls this: release_checks -> validate -> https://github.com/puppetlabs/puppetlabs_spec_helper/blob/main/lib/puppetlabs_spec_helper/rake_tasks.rb#L213

I think if this is the same as my workflows on my team, REFERENCE.MD is updated as part of the release prep workflow

@chelnak
Copy link
Contributor

chelnak commented Apr 25, 2023

Yeah I believe that is correct

Copy link
Contributor

@LukasAud LukasAud left a comment

Choose a reason for hiding this comment

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

LGTM

@LukasAud LukasAud merged commit 496c2b4 into puppetlabs:main Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants