puppetlabs / puppetlabs/puppet-resource_api
Provide access to facts hash through the context
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 27
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Use Case
Some providers would benefit from accessing system information through facts instead of duplicating the query (or worse, duplicating the query code) if it already exists.
Describe the Solution You Would Like
Add a facts accessor to a hash of all facts in the context classes implementing it as follows:
Base: raise an exception that this implementation does not support fact access.IO: take a static facts hash oninitialize, return that.Puppet: pass through access to Facter, using https://www.rubydoc.info/gems/facter/Facter#each-class_method.
Additional Context
Originally filed as https://tickets.puppetlabs.com/browse/PDK-1011
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 locating the context classes named Base, IO, and Puppet and reading how they are initialized. Check the Facter#each class method referenced in the issue, then verify that Base rejects access, IO returns its supplied facts hash, and Puppet exposes Facter's facts consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100