puppetlabs / puppetlabs/puppetlabs-node_encrypt
Warning messages in puppetserver.log due to node_decrypt having no return_type
Open
Nobody has claimed this yet.
bug
- Dominant language
- Ruby
- Stars
- 26
- Forks
- 21
- Avg merge
- 39m
- Merged PRs (30d)
- 1
Description
We get the following warning messages in our puppetserver.log relating to this module:
2024-05-13T09:09:35.299+02:00 WARN [qtp326372050-610476] [puppetserver] Puppet Deferred function node_decrypt has no return_type, unable to guarantee value type during compilation.
(file & line not available)
We are unsure what to do with this warning, or if it is actionable at all on our end. If this warning message is unnecessary, would it be possible to remove it?
- Puppet Version [7.28.0]
- node_encrypt Version [3.1.0]
- Platform [RHEL 8]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the warning with Puppet 7.28.0 and node_encrypt 3.1.0, then inspect the node_decrypt deferred function and its return type. Done means determining whether the warning is actionable and documenting or implementing the appropriate resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100