puppetlabs / puppetlabs/puppet-resource_api
Ability to use arbitrary type aliases from modules
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 27
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Currently, only built-in Puppet 4 data types are usable. This is because the type information is required on the agent, but Puppet has not made it available yet. This work is tracked in PUP-7197. Even once that is implemented, modules will have to wait until the functionality is widely available before being able to rely on it.
Originally tracked in https://tickets.puppetlabs.com/browse/PDK-532
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 with the Puppet 4 data types section in the linked resource-api README and review the status of PUP-7197, which tracks the required agent functionality. Confirm how PDK-532 relates to this issue; done means module-defined type aliases can be used rather than only built-in Puppet 4 data types.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100